While that is true, shoving that logic in to the database itself tends to indicate an anti pattern in the software that uses the database. It used to be lots o

While that is true, shoving that logic in to the database itself tends to indicate an anti pattern in the software that uses the database. It used to be lots of fun and highly optimal to write all sorts of procedures and triggers because it was the only fast and reliable way to do things, especially when your in-database-code was essential the only gatekeeper against a multiple owner database schema. The idea that you have one database schema that you are going to share with different applications seems bonkers to me at this point in time. Compute and storage resources are far cheaper than development, DBA and potential stagnation that a schema that doesn't have a single owner brings.