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

[ https://hibernate.onjira.com/browse/HHH-3799?page=com.atlassian.jira.plug... ] David Tarico commented on HHH-3799: ----------------------------------- I think the lack of an ID in an unsaved entity is exactly the problem here. The book "Java Persistence with Hibernate" by Christian Bauer and Gavin King talks in chapter 9 section 2.2 about implementing equality with a business key instead of the PK since the primary key is not assigned until the object is persisted. Like Shawn, we use one or more non-PK fields as the business key in the equals/hashcode so that we can use a set both before and after the objects are persisted and not worry about their identity changing and breaking the contract of a set. I think the issue here is that Hibernate simply cannot lazy load the entities in this PersistentSet and must hydrate them before adding them to the set. Perhaps it should be a configurable option if some users are using the ID and want the lazy loading, but when we've learned from authors on the Hibernate team not use the PK in equals/hashcode and have been doing this practice for many years, this definitely seems like an implementation bug with PersistentSet. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira