3 ms·

> And forgetting that extra predicate on deleted_at can have dangerous consequences as it accidentally returns data that’s no longer meant to be seen. For post

by fhub 3y ago

> And forgetting that extra predicate on deleted_at can have dangerous consequences as it accidentally returns data that’s no longer meant to be seen. For postgres you could consider using a view instead. See https://evilmartians.com/chronicles/soft-deletion-with-postgresql-but-with-logic-on-the-database https://evilmartians.com/chronicles/soft-deletion-with-postg...

icedchai 3y ago
This sort of logic is a good candidate for views. Of course, someone could choose not to use the view, but you can solve it with DB permissions, etc.
mike256 3y ago
You can do the same in other dbms. Just use an instead of delete trigger instead of the rule.