英文:
Is there a case in which JPA/Hibernate unidirectional OneToOne mapping may fail when used to model many-to-one relationship?
问题
我正在处理一个代码库，其中实体之间使用单向的 JPA/Hibernate @OneToOne 映射，而实际数据库关系的基数（cardinality）是一对多（many-to-one）。
然而，代码似乎工作正常，看起来从使用单向的 @OneToOne 到应该使用单向的 @ManyToOne 之间，并没有导致功能问题。
我想在代码库中解决这个问题，但需要一个集成测试来证明这个问题。
在哪种可测试的情况下，当使用单向的 @OneToOne 映射而在逻辑上应使用 @ManyToOne 时，Hibernate 会出现失败？
英文:
I'm working on a codebase where unidirectional JPA/Hibernate @OneToOne mapping is used on entities where actual database relationship cardinality between the entities is many-to-one.
However, it seems the code is working fine and it looks like there are no functional issues resulting from the use of unidirectional @OneToOne where unidirectional @ManyToOne should be used.
I would like to address this in the codebase but would need an integration test to demonstrate the problem.
Is there any testable case in which hibernate will fail when using unidirectional @OneToOne mapping where logically @ManyToOne should be used?
专注分享java语言的经验与见解，让所有开发者获益！
评论