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
Documentation states that to prevent accidental bulk changes, setting the option bulk to false will prevent against bulk changes in terms of PATCH or DELETE. There is however no implementation of this at the moment. This is not functional however.
Upon further investigation as well, there does not seem to be a header either that can prevent such accidental changes. Looking at the postgREST documentation, the suggested way to prevent accidental bulk changes would be through the use of a postgreSQL extension called pg-safeupdate. As such, this is beyond the scope of this package.
todo
Tidy up on Builder.js to remove redundancies brought by this discovery.
Update supabase & wiki documentation to provide the suggested way of minimising the risk of accidental bulk changes. (reference)
The text was updated successfully, but these errors were encountered:
I actually did put a check to prevent any bulk PATCH or DELETE if no filter is invoked. Nevertheless, the option bulk is still irrelevant and there is still the need to update the documentation.
Not so much of an issue, just an FYI.
Documentation states that to prevent accidental bulk changes, setting the option
bulk
tofalse
will prevent against bulk changes in terms ofPATCH
orDELETE
.There is however no implementation of this at the moment.This is not functional however.Upon further investigation as well, there does not seem to be a header either that can prevent such accidental changes. Looking at the postgREST documentation, the suggested way to prevent accidental bulk changes would be through the use of a postgreSQL extension called pg-safeupdate. As such, this is beyond the scope of this package.
todo
Builder.js
to remove redundancies brought by this discovery.The text was updated successfully, but these errors were encountered: