EF Core中配置多父实体至子实体的级联删除问题排查

问题场景 #

使用EF Core 7结合PostgreSQL，存在Customer、Supplier、Address三个实体，其中Customer和Supplier各自可关联多个Address。调用实体的RemoveAddress方法后，数据库中Address记录未被删除，仅对应外键被置为null。

核心代码 #

1. 实体地址属性定义：

private readonly List<Address> _addresses = new List<Address>();
public virtual IReadOnlyList<Address> Addresses => _addresses.ToList();

2. 实体配置类：

internal class CustomerConfiguration : IEntityTypeConfiguration<Customer>
{
    public void Configure(EntityTypeBuilder<Customer> builder)
    {
        builder.ToTable(nameof(Customer));
        builder.HasKey(x => x.Id);
        builder.HasMany(x => x.Addresses).WithOne()
            .OnDelete(DeleteBehavior.Cascade)
            .Metadata.PrincipalToDependent?.SetPropertyAccessMode(PropertyAccessMode.Field);
    }
}

internal class SupplierConfiguration : IEntityTypeConfiguration<Supplier>
{
    public void Configure(EntityTypeBuilder<Supplier> builder)
    {
        builder.ToTable(nameof(Supplier));
        builder.HasKey(x => x.Id);
        builder.HasMany(x => x.Addresses).WithOne()
            .OnDelete(DeleteBehavior.Cascade)
            .Metadata.PrincipalToDependent?.SetPropertyAccessMode(PropertyAccessMode.Field);
    }
}

3. 迁移脚本关键部分：

migrationBuilder.CreateTable(
    name: "Address",
    columns: table => new
    {
        Id = table.Column<int>(type: "integer", nullable: false)
            .Annotation("Npgsql:ValueGenerationStrategy", NpgsqlValueGenerationStrategy.IdentityByDefaultColumn),
        CustomerId = table.Column<int>(type: "integer", nullable: true),
        SupplierId = table.Column<int>(type: "integer", nullable: true)
    },
    constraints: table =>
    {
        table.PrimaryKey("PK_Address", x => x.Id);
        table.ForeignKey(
            name: "FK_Address_Customer_CustomerId",
            column: x => x.CustomerId,
            principalTable: "Customer",
            principalColumn: "Id",
            onDelete: ReferentialAction.Cascade);
        table.ForeignKey(
            name: "FK_Address_Supplier_SupplierId",
            column: x => x.SupplierId,
            principalTable: "Supplier",
            principalColumn: "Id",
            onDelete: ReferentialAction.Cascade);
    });

4. 删除地址方法：

public void RemoveAddress(int id)
{
    var address = _addresses.FirstOrDefault(a => a.Id == id);
    if (address != null)
    {
        _addresses.Remove(address);
    }
}

问题原因 #

1. 数据库级联删除的作用范围：配置的OnDelete(DeleteBehavior.Cascade)对应数据库层面的级联删除，仅在删除Customer或Supplier主实体时生效，不处理从集合中移除子实体的操作。
2. EF Core默认跟踪行为：由于Address的两个外键均为可空（可属于任意一个主实体），EF Core默认认为移除集合中的Address只是解除关联，而非删除实体，因此会将对应外键置为null。

解决方案 #

方案1：显式删除Address实体 #

在业务逻辑中，从集合移除Address后，显式通知EF Core删除该实体：

// 服务层示例代码
public void RemoveCustomerAddress(int customerId, int addressId)
{
    var customer = _context.Customers.Include(c => c.Addresses)
        .FirstOrDefault(c => c.Id == customerId);
    
    if (customer == null) return;
    
    var address = customer.Addresses.FirstOrDefault(a => a.Id == addressId);
    if (address != null)
    {
        customer.RemoveAddress(addressId);
        _context.Addresses.Remove(address); // 显式标记删除
    }
    
    _context.SaveChanges();
}

若遵循领域驱动设计，可通过标记删除+统一处理的方式实现：

// Address类新增删除标记
public bool IsDeleted { get; private set; }

public void MarkAsDeleted()
{
    IsDeleted = true;
}

// 修改Customer的RemoveAddress方法
public void RemoveAddress(int id)
{
    var address = _addresses.FirstOrDefault(a => a.Id == id);
    if (address != null)
    {
        _addresses.Remove(address);
        address.MarkAsDeleted();
    }
}

// DbContext重写SaveChanges统一处理删除
public override int SaveChanges()
{
    foreach (var entry in ChangeTracker.Entries<Address>()
             .Where(e => e.Entity.IsDeleted && e.State != EntityState.Deleted))
    {
        entry.State = EntityState.Deleted;
    }
    return base.SaveChanges();
}

方案2：配置客户端级联删除 #

修改实体配置，使用DeleteBehavior.ClientCascade，让EF Core在从集合移除子实体时自动标记删除：

// CustomerConfiguration修改
builder.HasMany(x => x.Addresses).WithOne()
    .OnDelete(DeleteBehavior.ClientCascade) // 客户端级联删除
    .Metadata.PrincipalToDependent?.SetPropertyAccessMode(PropertyAccessMode.Field);

// SupplierConfiguration做相同修改

注意：该方案要求EF Core必须跟踪Customer/Supplier及关联的Addresses集合（需通过Include加载），否则无法触发客户端级联删除逻辑。

补充说明 #

• 数据库层面的ReferentialAction.Cascade仅处理主实体删除场景，客户端移除子实体的行为由EF Core跟踪逻辑控制。
• 若Address只能属于Customer或Supplier中的一个，可添加数据库约束确保同一Address的两个外键仅有一个非空，避免数据不一致。

内容的提问来源于stack exchange，提问作者Gabe