Home/ Questions/Q 6769189
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T15:09:48+00:00

It’s not a specific question, more a general wondering. When you have to make

  • 0

It’s not a specific question, more a general wondering.

When you have to make a delete on multiple tables in a 1:M relationship, is it better to make a FK constraint with a cascade delete or join the tables in the delete statement.

I had an old project that had separate delete statements for related tables, and a few times some of the statements were not executed and data integrity was compromised. I had to make a decision between the two, so I was thinking a bit what would be a better solution.

There is also an option to make a stored procedure or a transaction.

So I am looking for an opinion or advice…?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If your database has proper RI defined for it then there shouldn’t be any case of compromised data integrity. All of your related tables should have declarative RI, which means that you can’t delete a parent while it still has children.

    Also, if you have code that is only deleting some of the rows at times then that is poor coding and poor testing. These kinds of actions should be a single transaction. Your suggestion of using a stored procedure is a great approach for solving that problem and is pretty standard.

    As has already been mentioned, cascading triggers have the danger of deleting rows that someone did not intend to delete. Consider that sometimes people might be accessing your data from somewhere outside of your application, especially when fixing data issues. When someone accidentally tries to delete the wrong parent and gets an RI error that’s good. When they accidentally try to delete the wrong parent and it not only deletes that parent but 20 children in 5 other tables, that’s bad.

    Also, cascading deletes are very hidden. If a developer is coding a delete for the parent then they should know that they have to use the delete stored procedure to take care of children. It’s much preferable to have a developer not code against that, get an error, and fix his code (or realize that he doesn’t really want to do all of that deleting) than it is to have a developer throw in a delete and have no one realize that it’s killing off children until the code has gone live.

    IMO, I prefer to have my developers knowledgeable about the application rather than make it easier for them to remain ignorant of it.

    • 0