2
Running an Edge Function when a row matches conditions
Source: supabase/supabase#14208 · opened by @MartinMalinda
I'm a frequent user of Airtable and besides web development I also do automations. In Airtable, automations (workflows) are frequently run when records in a table get in a certain state.
This kind of flow would be very intuitive for me.
For example I'd let someone change their own user profile record.
Then I'd react on the server side to the profile row change and do some additional cleanup. But I wouldn't have to do the cleanup directly from the client (as part of some transaction for example). This way I also wouldn't have to worry about permissions that much.
The user would do the minimal amount of changes and then the background logic would take care of the rest.
Is this the right way of thinking about things?
It's sort of an "observer pattern". I guess it has upsides and downsides.
<img width="1029" alt="Screenshot 2023-05-08 at 18 03 43" src="
This kind of flow would be very intuitive for me.
For example I'd let someone change their own user profile record.
Then I'd react on the server side to the profile row change and do some additional cleanup. But I wouldn't have to do the cleanup directly from the client (as part of some transaction for example). This way I also wouldn't have to worry about permissions that much.
The user would do the minimal amount of changes and then the background logic would take care of the rest.
Is this the right way of thinking about things?
It's sort of an "observer pattern". I guess it has upsides and downsides.
<img width="1029" alt="Screenshot 2023-05-08 at 18 03 43" src="
No pledges yet. Be the first to back this.
Comments
Similar requests
Add a "Duplicate row" action to the Table Editor
1 vote · 0 comments
Enable Syncing of Vault and Edge Function Secrets
1 vote · 0 comments
Support skipping conflicting rows during CSV import
1 vote · 0 comments
Edge Function runtime events
1 vote · 0 comments
Feature Request: Add Descriptions for Edge Functions
2 votes · 0 comments
No comments yet.