[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...
]
Shawn Clowater commented on HHH-3799:
-------------------------------------
In our case we hash off a single uuid property that is persisted with our entity. When we
create a new object we automatically generate the uuid so that we can identify the new
object with its generated PK when it comes back from the server to the client.
I voted for making the uuid our pk but users seem to hate having to do select * from table
where id = '1f822e76-f219-462c-9574-874cf813b15d' rather than id = 4, go figure.
So, your 'partial' fix would most likely be a full fix for us.
PersistentSet does not honor hashcode/equals contract when loaded
eagerly
-------------------------------------------------------------------------
Key: HHH-3799
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3799
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.3.1, 3.5.1
Reporter: Igor Vaynberg
Assignee: Gail Badner
Fix For: 3.5.x
Attachments: test.zip
when persistent set is loaded eagerly in some situations it calls hashcode on its items
before their field values are populated and then uses this incorrect hashcode to store
them in the set. this makes set items inaccessible by any collection items that rely on
hashcode such as contains(), remove(), etc.
attached is a simple maven test project that reproduces the error, unzip and mvn test to
run the test.
--
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