EF Core 7中如何在无子实体时删除父实体？

你提到的反向配置之所以无效，是因为一对多关系里外键定义在子实体（Employee）上，SQL Server原生的级联删除逻辑是父实体删除时自动删除关联子实体，反向的“子实体全删删父”属于业务逻辑，数据库本身不支持这种级联规则，需要通过以下几种方式手动实现：

方法1：业务代码中手动检查删除 #

每次删除子实体后，检查对应父实体是否还有剩余子实体，若没有则删除父实体：

public async Task DeleteEmployee(int employeeId)
{
    var employee = await _context.Employees
        .Include(e => e.Department)
        .FirstOrDefaultAsync(e => e.Id == employeeId);
    
    if (employee == null) return;
    
    var targetDepartment = employee.Department;
    _context.Employees.Remove(employee);
    await _context.SaveChangesAsync();

    // 检查该部门是否还有剩余员工
    if (!_context.Employees.Any(e => e.DepartmentId == targetDepartment.Id))
    {
        _context.Departments.Remove(targetDepartment);
        await _context.SaveChangesAsync();
    }
}

方法2：数据库触发器实现 #

直接在SQL Server中创建触发器，当Employees表删除记录后，自动检查对应Department是否还有员工，无则删除：

CREATE TRIGGER trg_CleanupEmptyDepartments
ON Employees
AFTER DELETE
AS
BEGIN
    SET NOCOUNT ON;

    -- 删除没有任何员工的部门
    DELETE d
    FROM Departments d
    WHERE d.Id IN (
        SELECT de.DepartmentId 
        FROM deleted de
        WHERE NOT EXISTS (
            SELECT 1 FROM Employees e WHERE e.DepartmentId = de.DepartmentId
        )
    );
END

方法3：重写DbContext的SaveChanges方法 #

通过拦截EF Core的保存操作，自动处理空父实体的删除逻辑，无需在业务代码中重复编写：

public class AppDbContext : DbContext
{
    public DbSet<Department> Departments { get; set; }
    public DbSet<Employee> Employees { get; set; }

    // 其他DbContext配置...

    public override async Task<int> SaveChangesAsync(CancellationToken cancellationToken = default)
    {
        // 获取所有被标记为删除的Employee
        var deletedEmployees = ChangeTracker.Entries<Employee>()
            .Where(entry => entry.State == EntityState.Deleted)
            .Select(entry => entry.Entity)
            .ToList();

        foreach (var deletedEmp in deletedEmployees)
        {
            // 查询对应部门（避免懒加载，直接用FindAsync）
            var department = await Departments.FindAsync(deletedEmp.DepartmentId, cancellationToken);
            if (department == null) continue;

            // 检查部门是否还有其他员工
            var hasRemainingEmployees = await Employees
                .AnyAsync(e => e.DepartmentId == department.Id && e.Id != deletedEmp.Id, cancellationToken);

            if (!hasRemainingEmployees)
            {
                // 标记部门为删除
                Departments.Remove(department);
            }
        }

        return await base.SaveChangesAsync(cancellationToken);
    }
}

补充说明 #

你之前尝试的反向配置，本质上还是和原配置等价的——因为EF Core会根据关系两端的配置自动识别外键位置，最终生成的数据库级联规则依然是“删除Department时自动删除关联Employee”，所以无法实现你需要的反向逻辑。

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