[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4992?page=c...
]
Julian Maughan commented on HHH-4992:
-------------------------------------
I've completed a port of the Hibernate 'read-only Session/Criteria' for
NHibernate. However, I'm having trouble getting the following tests to pass:
readonly/testMergeDetachedChildWithNewParentCommitWithReadOnlyChild [1] and
readonly/testGetChildMakeReadOnlyThenMergeDetachedChildWithNewParent [2]. Are these tests
expected to pass? They aren't marked 'FailureExpected', but neither has this
issue been Resolved.
Version is incremented when an inverse one-to-many collection is
dirtied by adding or removing read-only entities
-----------------------------------------------------------------------------------------------------------------
Key: HHH-4992
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4992
Project: Hibernate Core
Issue Type: Bug
Components: core
Reporter: Gail Badner
Assignee: Gail Badner
If a persistent, read-only entity is added to an inverse one-to-many association, and the
owning entity is versioned, then, when flushed, the collection is found to be dirty, the
owning entity's version is incremented, but the read-only entity is not actually added
or removed from collection.
This does not happen when the association is non-inverse.
This situation should at least be logged.
--
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