Introducing FOREIGN KEY constraint may cause cycles or multiple cascade paths - why?

Question

I\'ve been wrestling with this for a while and can\'t quite figure out what\'s happening. I have a Card entity which contains Sides (usually 2) - and both Cards and Sides h

Answer 1

Here's what I did. This will apply to all Circular relationships, hence you don't have to specify one by one inside OnModelCreating.

Steps

1. Remove last migration (dotnet ef migrations remove)
2. Add the following code snippet in your OnModelCreating

var cascadeFKs = modelBuilder.Model.GetEntityTypes()
    .SelectMany(t => t.GetForeignKeys())
    .Where(fk => !fk.IsOwnership && fk.DeleteBehavior == DeleteBehavior.Cascade);

foreach (var fk in cascadeFKs)
    fk.DeleteBehavior = DeleteBehavior.Restrict;

3. Create new migrations
4. Update database

This did the trick for me.