From: NHibernate J. <mik...@us...> - 2006-12-18 14:48:36
|
nosetter access strategy on <version> tag causes incorrect dirty check result ----------------------------------------------------------------------------- Key: NH-838 URL: http://jira.nhibernate.org/browse/NH-838 Project: NHibernate Type: Bug Components: Core Versions: 1.2.0.Beta2 Reporter: Bill Poole Priority: Minor Applying the "nosetter" property access strategy on the <version> element in a mapping file for an entity type seems to cause NHibernate to falsely detect a dirty condition for any entity instance of that type and issue an UPDATE against the database. Changing the access strategy to "field" immediately caused the UPDATEs no longer to be issued against the database. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nhibernate.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |