|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-05-24 12:36:45
|
[ http://216.121.112.228/browse/NH-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo closed NH-2727.
---------------------------
Resolution: Not an Issue
In the title you are describing the default behavior of DefaultDirtyCheckEventListener.
> Calling ISession.IsDirty Raises SaveOrUpdate Event
> --------------------------------------------------
>
> Key: NH-2727
> URL: http://216.121.112.228/browse/NH-2727
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0, 3.2.0Beta1
> Reporter: Ricardo Peres
> Attachments: FlushTest.zip
>
>
> When calling ISession.IsDirty() after loading an entity which lazy loads another one and doing nothing to them, the SaveOrUpdate event is raised on the lazy loaded entity.
> This doesn't happen all the time, only if the lazy loaded entity is not specifically loaded beforehand.
> The included test creates the DB and populates it with test records. The HIBERNATE_UNIQUE_KEY table must be created first, since SchemaUpdate does not create it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|