Spring JPA多对多自动保存问题及@OneToMany改造后外键异常求助

这个异常的核心原因是：保存新Index时，中间表INDEX_USER的INDEX_ID还未被数据库生成并关联，导致外键找不到父表INDEX的主键记录。以下是具体解决步骤：

1. 修正实体映射的关联关系 #

必须确保双向关联的正确性，同时维护复合主键的映射：

Index实体配置 #

@Entity
@Table(name = "INDEX")
public class Index {
    @Id
    @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "index_seq")
    @SequenceGenerator(name = "index_seq", sequenceName = "SEQ_INDEX", allocationSize = 1)
    @Column(name = "INDEX_ID")
    private Long id;

    // 关联中间表，mappedBy指向IndexUser中的index字段，级联持久化
    @OneToMany(mappedBy = "index", cascade = CascadeType.PERSIST, orphanRemoval = true)
    private List<IndexUser> indexUsers = new ArrayList<>();

    // 添加用户的方法，必须维护双向关联
    public void addUser(User user, boolean inCharge, boolean backup) {
        IndexUser indexUser = new IndexUser();
        indexUser.setIndex(this);
        indexUser.setUser(user);
        indexUser.setInCharge(inCharge ? 1 : 0);
        indexUser.setBackup(backup ? 1 : 0);
        
        if (!indexUsers.contains(indexUser)) {
            indexUsers.add(indexUser);
        }
    }

    // getter、setter省略
}

IndexUser中间实体配置 #

@Entity
@Table(name = "INDEX_USER")
@IdClass(IndexUserId.class) // 绑定复合主键类
public class IndexUser {
    @Id
    @ManyToOne(fetch = FetchType.LAZY)
    @JoinColumn(name = "INDEX_ID", nullable = false)
    private Index index;

    @Id
    @ManyToOne(fetch = FetchType.LAZY)
    @JoinColumn(name = "USER_ID", nullable = false)
    private User user;

    @Column(name = "IN_CHARGE")
    private Integer inCharge;

    @Column(name = "BACKUP")
    private Integer backup;

    // 重写equals和hashCode，基于复合主键字段
    @Override
    public boolean equals(Object o) {
        if (this == o) return true;
        if (o == null || getClass() != o.getClass()) return false;
        IndexUser indexUser = (IndexUser) o;
        return Objects.equals(index.getId(), indexUser.index.getId()) &&
               Objects.equals(user.getId(), indexUser.user.getId());
    }

    @Override
    public int hashCode() {
        return Objects.hash(index.getId(), user.getId());
    }

    // getter、setter省略
}

复合主键类IndexUserId #

public class IndexUserId implements Serializable {
    private Long index;
    private Long user;

    // 无参、全参构造方法
    public IndexUserId() {}
    public IndexUserId(Long index, Long user) {
        this.index = index;
        this.user = user;
    }

    // 重写equals和hashCode
    @Override
    public boolean equals(Object o) {
        if (this == o) return true;
        if (o == null || getClass() != o.getClass()) return false;
        IndexUserId that = (IndexUserId) o;
        return Objects.equals(index, that.index) &&
               Objects.equals(user, that.user);
    }

    @Override
    public int hashCode() {
        return Objects.hash(index, user);
    }
}

2. 调整保存逻辑与级联策略 #

• 使用CascadeType.PERSIST级联策略：Hibernate会先持久化Index，获取数据库生成的INDEX_ID后，再插入中间表INDEX_USER，从根源避免外键找不到的问题。
• 若关联的User是新创建的，需先调用userRepository.save(user)将其持久化；若User是从数据库查询的持久化对象，可直接关联使用。

3. 验证数据库外键约束 #

• 确认INDEX_USER表的INDEX_ID外键确实指向INDEX表的INDEX_ID，USER_ID外键指向USER表的USER_ID。
• 检查字段类型一致性：确保父表主键与中间表外键都是NUMBER(8)类型。

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