Still incorrect FK circularity errors ------------------------------------- Key: ANN-730 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-730 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Environment: Hibernate 3.2.6.ga, HEM3.3.2.ga, HAN3.3.1.ga, JSE 1.6, DB2 8.2 Reporter: Lars Heyden Attachments: cyclic-test.zip This bug is related to ANN-694 (and some other issues). Correctly mapped JoinedSubclasses still get reported to have circularities in their FKs which is not the case. To reproduce the bug at least four entity classes must be in a joined class hierarchy. As in ANN-694 there is a workaround by renaming the tables to force another processing order. I've provided a small test case: It consists of four entities ClassA, ClassB, ClassC and ClassD mapped with InheritanceType.JOINED to the tables "class_a", "class_b", "class_c" and "class_1d". Because ClassD maps to table "class_1d" it gets processed first by the circularity check which raises the error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira