[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-1660) PersistentSet becomes dirty on call to .remove(Object obj) even if obj is not in set
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1660?page=all ]
Steve Ebersole closed HHH-1660:
-------------------------------
Resolution: Duplicate
PersistentSet becomes dirty on call to .remove(Object obj) even if
obj is not in set
------------------------------------------------------------------------------------
Key: HHH-1660
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1660
Project: Hibernate3
Type: Improvement
Components: core
Versions: 3.1.3
Environment: Hib 3.1.3
Reporter: Frank Durden
Priority: Minor
Hi,
It seems that a PersistentSet (and maybe other collections too) are marked as dirty on
calls to .remove(Object o) even if the set does not actually contain the said object. On
flush this triggers unnecessary updates to the version number of the object containing the
set, which is unnecessary since nothing has actually changed.
Thank you!
--
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