Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-119
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-119
Summary: Possible bug with versioning and collections
Type: Bug
Status: Assigned
Priority: Critical
Project: Hibernate2
Components:
core
Assignee: Gavin King
Reporter: Gavin King
Created: Mon, 2 Jun 2003 7:08 PM
Updated: Mon, 2 Jun 2003 7:08 PM
Description:
I ran into this problem when writing an audit interceptor based on our earlier discussions. Basically searchForDirtyCollections does not seem to return true when a collection reference has changed (i.e. the user set the collection to be a different collection from the one loaded). Looking at the code, searchForDirtyCollections just checks to see if the entry is dirty consequently when a collection is newly wrapped it does not appear dirty to that method.
The upshot is that if the object is versioned and a collection reference is changed it will not update the version number. This is not major problem because users can always use addAll and clear to avoid changing the reference.
Just thought you might like to know.
Regards,
Ali Ibrahim
Vecna Technologies
from:
https://sourceforge.net/forum/forum.php?thread_id=877654&forum_id=128638
---------------------------------------------------------------------
JIRA INFORMATION:
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/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
