聚合根内实体关联引发Spring Data JDBC删插外键约束异常求助

问题背景 #

我有一个包含两个实体的聚合根，其中Membership实体引用Department实体。由于数据库存在外键约束，Spring Data JDBC执行删除再重新插入数据时抛出错误：Key (department_id)=(0DJ61WH12EDHH) is not present in table "departments"。

业务规则 #

• 删除Organization时，需删除所有关联的Department和Membership（不删除User）
• 必须先解除Membership对Department的引用，才能删除Department
• 删除Membership时，不得删除关联的Department和Organization

实体结构 #

class Organization { // 聚合根
  @Id
  private Integer id;

  @MappedCollection(idColumn = "organization_id")
  private Set<Department> departments = new HashSet<>();

  @MappedCollection(idColumn = "organization_id")
  private Set<Membership> memberships = new HashSet<>();
}

class Department {
  @Id
  private Integer id;
}

class Membership {
  @Id
  private Integer id;

  @Column("organization_id")
  private AggregateReference<Organization, String> organization;

  @Column("user_id")
  private AggregateReference<User, String> user;

  @Column("department_id")
  private AggregateReference<Department, String> department;
}

问题核心：修改聚合根时，Spring Data JDBC会先删除所有子实体再重新插入，但Membership的插入顺序早于Department，导致违反外键约束。不想删除数据库约束，尝试将引用改为实体引用未成功且不符合DDD规范，寻求可行方案。

可行解决方案 #

方案1：调整集合类型为List并利用字段声明顺序控制插入顺序 #

Set是无序集合，Spring Data JDBC无法保证子实体的处理顺序。将集合改为List后，框架会按照字段在类中的声明顺序处理子实体，确保Department先被插入，再插入Membership。

修改后的Organization类：

class Organization { // 聚合根
  @Id
  private Integer id;

  @MappedCollection(idColumn = "organization_id")
  private List<Department> departments = new ArrayList<>();

  @MappedCollection(idColumn = "organization_id")
  private List<Membership> memberships = new ArrayList<>();
}

方案2：自定义聚合根保存逻辑 #

如果默认CRUD逻辑不满足需求，可自定义Repository实现，手动控制删除和插入的顺序，完全规避顺序问题：

1. 保存聚合根本身
2. 删除现有Membership
3. 删除不在当前聚合中的Department
4. 插入/更新Department
5. 插入Membership

示例实现：

@Repository
public class OrganizationRepositoryImpl implements OrganizationCustomRepository {

    private final JdbcTemplate jdbcTemplate;

    public OrganizationRepositoryImpl(JdbcTemplate jdbcTemplate) {
        this.jdbcTemplate = jdbcTemplate;
    }

    @Override
    public void saveOrganization(Organization organization) {
        // 保存聚合根
        jdbcTemplate.update(
            "INSERT INTO organizations (id) VALUES (?) ON CONFLICT (id) DO NOTHING",
            organization.getId()
        );

        // 删除所有关联Membership
        jdbcTemplate.update(
            "DELETE FROM memberships WHERE organization_id = ?",
            organization.getId()
        );

        // 删除已移除的Department
        List<Integer> currentDeptIds = organization.getDepartments()
            .stream()
            .map(Department::getId)
            .toList();
        
        if (currentDeptIds.isEmpty()) {
            jdbcTemplate.update(
                "DELETE FROM departments WHERE organization_id = ?",
                organization.getId()
            );
        } else {
            jdbcTemplate.update(
                "DELETE FROM departments WHERE organization_id = ? AND id NOT IN (?)",
                organization.getId(), currentDeptIds
            );
        }

        // 插入/更新Department
        for (Department dept : organization.getDepartments()) {
            jdbcTemplate.update(
                "INSERT INTO departments (id, organization_id) VALUES (?, ?) " +
                "ON CONFLICT (id) DO UPDATE SET organization_id = EXCLUDED.organization_id",
                dept.getId(), organization.getId()
            );
        }

        // 插入Membership
        for (Membership membership : organization.getMemberships()) {
            jdbcTemplate.update(
                "INSERT INTO memberships (id, organization_id, user_id, department_id) VALUES (?, ?, ?, ?)",
                membership.getId(),
                membership.getOrganization().getId(),
                membership.getUser().getId(),
                membership.getDepartment() != null ? membership.getDepartment().getId() : null
            );
        }
    }
}

方案3：数据库层面设置延迟外键约束 #

将memberships.department_id的外键约束设置为延迟检查，让数据库在事务提交时才验证约束，而非每条语句执行后立即检查。这样即使Membership先插入，只要事务结束前Department已存在，就不会触发约束错误。

以PostgreSQL为例，修改约束的SQL：

-- 删除原有约束
ALTER TABLE memberships
DROP CONSTRAINT memberships_department_id_fkey;

-- 添加延迟检查的外键约束
ALTER TABLE memberships
ADD CONSTRAINT memberships_department_id_fkey
FOREIGN KEY (department_id) REFERENCES departments(id)
DEFERRABLE INITIALLY DEFERRED;

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