Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
After toying a little more with Delete actions for referentials, I think the rational of having the CASCADE DELETE as default is the following: having to DELETE the children before the parent is ...
Answer
#1: Initial revision
by
Alexei
·
2020-10-16T13:40:22Z (about 4 years ago)
After toying a little more with Delete actions for referentials, I think the rational of having the CASCADE DELETE as default is the following: - having to DELETE the children before the parent is not actually trivial (clearing the navigation properties collections first leads to a save error, removing the children and saving creates lots of delete queries). - back in the days there was a more database centered (first) approach (e.g. much business logic in stored procedures, many queries to be run directly from a SQL client) and less focus on automatic testing. Since the logic is more "code-first" now and more focus on test coverage it is harder to accidently remove data in cascade.