[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... ] Dirk commented on HHH-5187: --------------------------- I would like to apologize for my harsh words. I felt myself offended when I read your discussion. I could not see any reason for a "user error" or why I was called dud. You would probably not like that either if you think you have nothing done wrong. So I was focused on that.. Anyway. Actually I pointed you to section 3.2.4.1 Merging Detached Entity State, p.51 in HHH-4135. I attached a JUnit test case, I mentioned that I also tested it with EclipseLink and that it behaves as expected. You closed it eagerly with a comment that surprised me and others. So what else do you expect I need to do here? What I really appreciate is that you discussed this in your team and elaborate on it. My hope was that no further mapping is needed and that CascadeType.MERGE is only considered for initialized entities. But ok, I see your optimization point and after knowing what you are doing here I understand now why Hibernate behaves this way. Nevertheless if you introduce a (optional) way to retain these non-initialized associations after merge I would definitively vote for it and I think many other Hibernate users as well. Thanks. -- 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