JPA集成测试触发参照完整性约束异常，生产环境运行正常

为Post实体新增关联POST_HISTORY表的latestPostVersion字段后，生产环境代码运行正常，但Junit DataJpa集成测试中执行findAll方法时触发参照完整性约束违例，findById方法则无异常。我们希望理解原因，并在保留原有代码的前提下优雅修复测试（将关联改为OneToMany返回Set可使测试和生产都正常，但不想改动核心代码）。

实体映射代码 #

Post实体 #

@Entity
@Table(name = "POST")
@Setter
public class Post
    extends Serializable
{
    private long id;
    private int version;
    private String title;
    private String body;
    //.. 更多字段
    
    private PostHistory latestPostVersion;
    
    @Column(name = "ID", nullable = false)
    public long getId()
    {
        return id;
    }
    
    @Version
    @Column(name = "VERSION", nullable = false)
    public int getVersion()
    {
        return version;
    }

    @OneToOne(fetch = FetchType.EAGER)
    @JoinColumn(name = "ID", referencedColumnName = "ID", insertable = false, updatable = false)
    @JoinColumn(name = "VERSION", referencedColumnName = "VERSION", insertable = false, updatable = false)
    public PostHistory getLatestPostVersion()
    {
        return latestPostVersion;
    }

    //... 其他getter方法
}

PostHistory实体（注：类名存在笔误，实际应为PostHistory） #

@Entity
@Table(name = "POST_HISTORY")
@Setter
public class Post
    extends Serializable
{
    private long id;
    private int version;
    private String createBy;
    private Instant createDate;
    private String title;
    
    @Column(name = "ID", nullable = false)
    public long getId()
    {
        return id;
    }
    
    @Column(name = "VERSION", nullable = false)
    public int getVersion()
    {
        return version;
    }

     //... 更多映射方法
}

服务层保存逻辑（生产环境运行正常） #

private ClientPost savePost(ClientPost post, String updatedBy){
        Post dbPost = convertToDbModel(post);

        Post persistedPost =
            postRepository.saveAndFlush(post);

        PostHistory persistedPostHistory =
            postHistoryRepository.saveAndFlush(
                new PostHistory(persistedPost, updatedBy));
                
        return convertToApiModel(persistedPost, persistedPostHistory);
}

测试代码及报错 #

测试类代码 #

@Execution(ExecutionMode.CONCURRENT)
@DataJpaTest(showSql = false)
class PostRepositoryTest
{
    @Autowired
    private TestEntityManager entityManager;

    @Autowired
    private PostRepository repository;

    @BeforeEach
    void init()
    {
        Post post = new Post();
        post.setTitle("Title");
        // ... 填充其他字段
        post.setLatestPostVersion(null);
        
        entityManager.persist(post);
    }
    
    @Test
    void findAll_existingPosts_returnsAllPost()
    {
        List<Post> posts = repository.findAll();
        assertEquals(1, posts.size());
    }
}

错误信息 #

Referential integrity constraint violation: "FK7ITU2SCAYHBAV3TA9DU94CDA3: PUBLIC.POST FOREIGN KEY(ID, VERSION) REFERENCES PUBLIC.POST_HISTORY(ID, VERSION) (CAST(1902 AS BIGINT), 0)"; SQL statement:
insert into post (version, ...,  id) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [23506-214]

补充表结构 #

POST表 #

ID bigInt not null PrimaryKey
TITLE varchar not null
BODY varchar default null
POST_HISTORY_ID bigInt key: MULTIPLE default null
POST_HISTORY_VERSION bigInt default null

POST_FK_POST_HISTORY owner POST refTable POST_HISTORY refObject PRIMARY

POST_HISTORY表 #

ID bigInt not null PrimaryKey
VERSION bigInt not null PrimaryKey
TITLE varchar not null
USER varchar not null
TIMESTAMP datetime not null

原因分析 #

1. Schema生成逻辑与实际外键不匹配：测试环境中Hibernate自动生成Schema时，会根据Post实体的@OneToOne关联配置，错误地将POST表的(ID, VERSION)作为外键关联到POST_HISTORY的主键，而生产环境实际外键是POST表的POST_HISTORY_ID和POST_HISTORY_VERSION。这种差异导致测试时仅持久化Post会触发错误的外键约束。
2. EAGER加载的触发时机：findAll是批量查询，会立即触发EAGER关联的加载逻辑，进而触发外键约束检查；而findById为单条查询，Hibernate可能延迟关联加载，不会立即触发约束验证。
3. 测试数据不完整：测试初始化仅创建Post，未创建对应的PostHistory记录，违反了测试环境自动生成的错误外键约束。

优雅修复方案（保留原有核心代码） #

方案1：补全测试初始化数据 #

在测试的init方法中同步创建并持久化对应的PostHistory，满足外键约束要求：

@BeforeEach
void init()
{
    Post post = new Post();
    post.setTitle("Title");
    // ... 填充其他字段
    
    // 先持久化Post并刷新
    entityManager.persist(post);
    entityManager.flush();
    
    // 创建匹配的PostHistory并持久化
    PostHistory postHistory = new PostHistory();
    postHistory.setId(post.getId());
    postHistory.setVersion(post.getVersion());
    postHistory.setCreateBy("test-user");
    postHistory.setCreateDate(Instant.now());
    postHistory.setTitle(post.getTitle());
    // 填充其他必要字段
    entityManager.persist(postHistory);
}

方案2：测试环境使用生产一致的Schema #

禁用Hibernate自动生成Schema，改用生产环境的Schema脚本初始化测试数据库：

@DataJpaTest(showSql = false, properties = {
    "spring.jpa.hibernate.ddl-auto=none",
    "spring.sql.init.schema-locations=classpath:sql/production-schema.sql" // 替换为实际生产Schema路径
})

方案3：临时调整关联加载策略（不推荐） #

将@OneToOne的fetch改为FetchType.LAZY，避免findAll时立即加载关联触发约束检查，但此方案会改变生产环境的加载行为，可能引发其他问题，仅作为临时应急方案。

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