Introducing FOREIGN KEY constraint may cause cycles or multiple cascade paths

by

All relationships in your model are required because all foreign key properties (CountryId, RegionId, CityId) are not nullable. For required one-to-many relationships EF will enable cascading delete by convention.

Country and Region have multiple delete paths to the Store table, for example if you delete a Country the related Stores can be deleted via three different cascading paths (which is not allowed with SQL Server):

  • Country -> Store
  • Country -> Region -> Store
  • Country -> Region -> City -> Store

You must avoid such ambiguous delete paths by either disabling cascading delete using Fluent API or by defining some of the relationships as optional (with a nullable foreign key Guid?).

Or remove the Stores collections (and the inverse references and FK properties) from all entities except City. To me those collections look redundant because you can find all stores in a Country by navigating through the Regions.Cities.Stores collections.

More Related Contents:

  1. Improving bulk insert performance in Entity framework [duplicate]
  2. ORM Entities vs. Domain Entities under Entity Framework 6.0
  3. Unique Constraint in Entity Framework Code First
  4. The specified type member ‘Date’ is not supported in LINQ to Entities Exception
  5. How to ensure proxies are created when using the repository pattern with entity framework?
  6. Entity Framework validation with partial updates
  7. Solution for “Validation failed for one or more entities. See ‘EntityValidationErrors’ property for more details.”
  8. NOT using repository pattern, use the ORM as is (EF)
  9. How do you update an edmx file with database changes?
  10. Cascading deletes with Entity Framework – Related entities deleted by EF
  11. Entity framework core update many to many
  12. Order navigation properties when using Include and/or Select methods with EF 4.1 Code-First?
  13. EF Query With Conditional Include
  14. Entity Framework CTP 4 – Code First Custom Database Initializer
  15. How do I singularize my tables in EF Code First?
  16. Set decimal(16, 3) for a column in Code First Approach in EF4.3 [duplicate]
  17. How to create index in Entity Framework 6.2 with code first
  18. Upgrade EF 4 EDMX to EF 6
  19. DbSet.Find method ridiculously slow compared to .SingleOrDefault on ID
  20. ObjectContext.Refresh()?
  21. An object with the same key already exists in the ObjectStateManager. The ObjectStateManager cannot track multiple objects with the same key
  22. Stuffing an anonymous type in ViewBag causing model binder issues
  23. What is the syntax for self referencing foreign keys in EF Code First?
  24. what is difference between a Model and an Entity
  25. check constraint entity framework
  26. int to string in Entity Framework
  27. Changes in IDENTITY column after EF core 3
  28. What would cause the Entity Framework to save an unloaded (but lazy loadable) reference over existing data?
  29. DbContext AutoDetectChangesEnabled set to false detecting changes
  30. .NET 4.5 Beta DbGeography NotImplementedException

Leave a Comment