From: NHibernate J. <nh...@gm...> - 2010-02-03 15:58:30
|
[ http://nhjira.koah.net/browse/NH-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Bakken updated NH-2100: ---------------------------- Attachment: NH.zip This set of tests contains examples of how calls to Refresh() in the second transaction can fix this issue. > Entity version updated when no update necessary. > ------------------------------------------------ > > Key: NH-2100 > URL: http://nhjira.koah.net/browse/NH-2100 > Project: NHibernate > Issue Type: Bug > Components: Core > Affects Versions: 2.1.2.GA > Reporter: Luke Bakken > Priority: Major > Attachments: NH.zip, NH.zip > > > I have a test case with two classes in a many-to-many relationship. Tests One and Two show failing cases where I would expect the version to not change, test Three shows a case where opening an entirely different session has the expected results. > Stepping through the NH source I can see that in the failing cases the PersistentBag associated with Class2List in Class1 does not have a populated Snapshot - this is why NH forces the collection to be dirty when the transaction ends. I would expect that adding items to a collection, calling Save() and then Commit() would update the Snapshot collection correctly in this case so a second Session is not necessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nhjira.koah.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |