[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... ] Bjarne Saebuck commented on HHH-3799: ------------------------------------- +1 As somebody posted before we also have two different identifiers: The "normal" primary key which is a numeric sequence value and a generated GUID which is used on Java side to guaranty uniqueness of newly created objects after transfer them from client to server and vice versa. So the GUID is taken to generate the HashCode. On database side the GUID of course is a column with an unique constraint but we can not take this as primary key because the customer would have his problem with "handling" such a long id. At debugging we saw that first time hashCode is called, the id is already known but no other fields, so wouldn´t it solve the problem if we could tell hibernate to also load the GUID field (or what field ever...) when it loads the id so that GUID is known at the same time as the id and can be used to generate the hashcode? Is there already any way to do so? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira