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.
Coming to my question: why have DELETE CASCADE as an implicit option for foreign keys in Entity Framework Core?