[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5187) Allow some control over whether or not an association is loaded via a join on the merge path

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5187?page=c... ] Steve Ebersole commented on HHH-5187: ------------------------------------- Actually, I'll tell you the "funniest part"... How many times we have to listen to "you violate the spec". I'll tell you what, why don't you point out the section of the spec that we violate here? Secondly what we do here is an optimization. The "eager load" is done by a single SQL with joins that is determined when the SessionFactory starts up based on associations paths marked with merge cascading (did you even read the discussion?). As far as EclipseLink, I have no clue what they do. I generally do not have time to go leisurely peruse their code base on my "down time". I'd imagine they do what I'd call the non-optimized case where they load each detached association one by one. That seemingly works more along the lines of your expectation. As we said in this attached discussion (seriously, did you even read it?) we would be open to a few ways to allow these non-initialized associations to remain non-initialized in the managed graph. Perhaps instead of being insulting you could comment in constructive means on those approaches? Just a thought... -- 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