[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3799) PersistentSet does not honor hashcode/equals contract when loaded eagerly

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3799?page=c... ] Jeff Payne commented on HHH-3799: --------------------------------- Seems like the real problem is that the general contract of the Collection methods is broken in this scenario. Object graph traversal is a commonly used mechanism. In fact, isn't that one of the reasons that mapping configs allow us to define a default fetch strategy, so that when the graph is traversed we can control how the associations are loaded? The workaround above should at least be part of the documentation as a workaround for known limitation. Also, the documentation section cited is concerned with how the joins in the query are written, explicitly vs. implicitly. This bug has to do with a collection association that isn't even mentioned in the query. The query-based workaround simply eagerly fetches the many-to-one association. -- 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