You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently had an embarrassing incident where one of our triggers were accidentally re-entrant, e.g. the trigger was invoked when editing a table, and on update of that table the same trigger was invoked again, ad infinitum.
This was completely accidental, and in part caused by a developer error in enabling this trigger when it shouldn't have been. Column based selective-updates kind of help, but in no-way help to solidly prevent this kind of scenario happening again. What we're looking for is a way to indicate from an admin context (this is important, as if unauthorised users are allowed to do this, the app's internal state may be left inconsistent), that a trigger that is on a table shouldn't be able to be invoked.
The team was helpful on the Discord, and pointed me to this issue: #1241 , but it isn't quite what I'm talking about.
Cheers
The text was updated successfully, but these errors were encountered:
Hi,
We recently had an embarrassing incident where one of our triggers were accidentally re-entrant, e.g. the trigger was invoked when editing a table, and on update of that table the same trigger was invoked again, ad infinitum.
This was completely accidental, and in part caused by a developer error in enabling this trigger when it shouldn't have been. Column based selective-updates kind of help, but in no-way help to solidly prevent this kind of scenario happening again. What we're looking for is a way to indicate from an admin context (this is important, as if unauthorised users are allowed to do this, the app's internal state may be left inconsistent), that a trigger that is on a table shouldn't be able to be invoked.
The team was helpful on the Discord, and pointed me to this issue: #1241 , but it isn't quite what I'm talking about.
Cheers
The text was updated successfully, but these errors were encountered: