This is coming up because we contracted out development of an integration with another app. They wrote a process to sync data between our schema and the new app's schema. When they checked it in, they were using raw inserts instead of some existing stored procs that did additional housekeeping.
If we had proper constraints in the DB we could have had cascading updates and the procs would have been unnecessary, or at least the inserts would have failed immediately instead of creating inconsistent data.
So it's not necessarily procs that I want, it's that somehow the data integrity should be managed in the DB, so there's no way for a developer to write code that breaks our data.
If we had proper constraints in the DB we could have had cascading updates and the procs would have been unnecessary, or at least the inserts would have failed immediately instead of creating inconsistent data.
So it's not necessarily procs that I want, it's that somehow the data integrity should be managed in the DB, so there's no way for a developer to write code that breaks our data.