Cascading deletes with Entity Framework – Related entities deleted by EF

by

This is exactly how cascading deletes behaves in EF. Setting Cascade on a relation in EF designer instructs EF to execute DELETE statement for each loaded realated entity. It doesn’t say anything about ON CASCADE DELETE in the database.

Setting Cascade deletion when using EF needs two steps:

  • Set Cascade on relation in EF designer. This instruct context that all loaded related entities must be deleted prior to deletion of the parent entity. If this doesn’t happen EF will throw exception because internal state will detect that loaded childs are not related to any existing parent entity even the relation is required. I’m not sure if this happens before execution of delete statement of the parent entity or after but there is no difference. EF doesn’t reload related entities after executing modifications so it simply doesn’t know about cascade deletes triggered in the database.
  • Set ON CASCADE DELETE on relation in database. This will instruct SQL to delete all related records which were not loaded to context in the time of deleting the parent.

The implementation of cascade deletes in EF is strange and quite inefficient but this is how it behaves and if you want to use it, you must modify your application to behaves correctly in this scenario.

More Related Contents:

  1. How do you ensure Cascade Delete is enabled on a table relationship in EF Code first?
  2. ASP.NET MVC 2.0 Implementation of searching in jqgrid
  3. Code First: Independent associations vs. Foreign key associations?
  4. Code-first vs Model/Database-first [closed]
  5. Entity Framework: “Store update, insert, or delete statement affected an unexpected number of rows (0).” [closed]
  6. Unique Key constraints for multiple columns in Entity Framework
  7. Entity Framework 6 Code first Default value
  8. Database first create entity framework 6.1.1 model using system.data.sqlite 1.0.93
  9. EF Code First “Invalid column name ‘Discriminator'” but no inheritance
  10. Improve navigation property names when reverse engineering a database
  11. How to configure ProviderManifestToken for EF Code First
  12. Entity Framework One-To-One Mapping Issues
  13. Can I specify global mapping rules in Entity Framework Code First?
  14. The specified named connection is either not found in the configuration, not intended to be used with the EntityClient provider, or not valid
  15. Entity Framework loading child collection with sort order
  16. How can I delete 1,000 rows with EF6?
  17. Entity Framework 4 selective lazy loading properties
  18. Equivalent for .HasOptional in Entity Framework Core 1 (EF7)
  19. When should I call SaveChanges() when creating 1000’s of Entity Framework objects? (like during an import)
  20. Adding Validation Attributes With an Entity Framework Data Model
  21. Ramifications of DbSet.Create versus new Entity()
  22. How to pass parameters to the DbContext.Database.ExecuteSqlCommand method?
  23. Using EF Core ThenInclude() on Junction tables
  24. How to update not every fields of an object using Entity Framework and EntityState.Modified
  25. Keyword not supported: “data source” initializing Entity Framework Context
  26. Entity Framework Data Annotations Set StringLength VarChar
  27. What is the best practice in EF Core for using parallel async calls with an Injected DbContext?
  28. EF 4.1 loading filtered child collections not working for many-to-many
  29. How to map Table per Type (TPT) inheritance in Entity designer?
  30. DbContext AutoDetectChangesEnabled set to false detecting changes

Leave a Comment