DDD EF Core Remove issue

Let’s say we have a classes:

public class Order 
{
    public int Id { get; set; }
    public List<OrderItem> OrderItems { get; set; }
    // other properties
}
public class OrderItem
{
    public int Id { get; set; }
    public int OrderId { get; set; }
    public Order Order { get; set; }
    // other properties
}

Order has primary key on Id property, OrderItem as well. OrderItem has foreign key to Order with OrderId property. Simple as that. Both are autoincremented.

Is there any way to remove OrderItem from Order with RemoveOrderItem defined method in Order class with using Entity Framework Core and not setting primary key on two fields (Id, OrderId) in OrderItem class (or any different key breaking changes workarounds)?

SO

[macgyver76]

I don’t use any of “Cascade Delete” EF Core functionality because I treat it as anti-pattern.

I agree. Hovewer OrderEntityTypeConfiguration class you provide sets delete rule to cascade when using migrations.

By the way. Here is how I set DeleteBehavior to Restrict globally to avoid cascade.

protected override void OnModelCreating(ModelBuilder modelBuilder)
{
    foreach (var relationship in modelBuilder.Model.GetEntityTypes().SelectMany(e => e.GetForeignKeys()))
    {
        relationship.DeleteBehavior = DeleteBehavior.Restrict;
    }
}

[macgyver76]

I came up with workaround. If your existing relationship do not use cascade - solution is to set DeleteBehavior to Cascade and then use Add-Migration command to generate migration files and update snapshot model but before running Update-Database you need to commend out Up method in migration file in order to not set cascade to database. Indeed, we have cascade in EF but not in database.

@kgrzybek - thanks for your commitment and I am looking forward to new DDD stuff in this repo.