[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1?page=comm... ] Steve Ebersole commented on HHH-1: ---------------------------------- This limitation regarding <join/>s is not even within the realm of control for this solution. And actually the same limitation would hold as well in the case of <joined-subclass/>. The reason is that it is actually the persister which performs the atomic inserts, not the actions. Example: class Super { ... } class Sub extends Super { ... } For each entity creation here we have exactly one entity insert action even though we will have 2 inserts commands executed (again, same thing for <join/>). Again, this is controlled by the persister, not the action. To properly account for those scenarios, we would need to tweak the algorithm such that it could group together Sub entity insertions within a given relational dependency chain and then have the atomic inserts performed together for any given level of dependency. There are a couple of way to achieve that aspect. I'll give some thought as to the most proficient way to to it. -- 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