Entity Framework Code First: FOREIGN KEY constraint may cause cycles or multiple cascade paths

Question

Entity Framework Code First can generate the DB for the following POCOs.

public class Item {
    public int Id { get; set; }
    public string Name { get; se         


        

Answer 1

I decided to just remove the cascade delete convention.

 protected override void OnModelCreating(DbModelBuilder modelBuilder) {
        base.OnModelCreating(modelBuilder);

        modelBuilder.Conventions.Remove();
        modelBuilder.Conventions.Remove();

    }

The reasons are:

• I prefer to mark records deleted or deactivated for audit purposes.
• At most I delete just the junction / mapping tables.
• With an ORM It is relatively trivial to loop through and delete child records in the rare case I need to.

Thank you Ladislav Mrnka pointing me in the right direction.