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
I have noticed some time ago that Entity Framework assumes a CASCADE behaviour (implicit value, if not specified) for referential constraints (FKs) when deleting items. This means that by default, ...
#1: Initial revision
by
Alexei
·
2020-10-12T11:11:25Z (about 4 years ago)
What is the rationale of having Cascade as a DeleteAction in EntityFramework.Core?
I have noticed some time ago that Entity Framework assumes a CASCADE behaviour (implicit value, if not specified) for referential constraints (FKs) when deleting items. This means that by default, if a parent record is removed, all descendants are removed. I remember that back in the days, when database first was still heavily used and database objects were created through SQL scripts rather than through migrations, I received the advice to never use DELETE CASCADE to prevent unwanted deleted items. Back then that made perfect sense [since recovering deleted data is not exactly trivial](https://www.mssqltips.com/sqlservertip/3160/recover-deleted-sql-server-data-and-tables-with-the-help-of-transaction-log-and-lsns/). Coming to my question: why have DELETE CASCADE as an implicit option for foreign keys in Entity Framework Core?