nhibernate-issues

[nhibernate-issues] [JIRA] Created: (NH-838) nosetter access strategy on <version> tag causes incorrect dirty check result

[NHibernate J. <mik...@us...>]

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

[nhibernate-issues] [JIRA] Commented: (NH-838) nosetter access strategy on <version> tag causes incorrect dirty check result

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-838?page=comments#action_14700 ]
     
Sergey Koshcheyev commented on NH-838:
--------------------------------------

Please supply a simple test case.

> 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

[nhibernate-issues] [JIRA] Updated: (NH-838) nosetter access strategy on <version> tag causes incorrect dirty check result

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-838?page=all ]

Sergey Koshcheyev updated NH-838:
---------------------------------

    Fix Version: LATER

> 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
>      Fix For: LATER

>
> 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

[nhibernate-issues] [JIRA] Closed: (NH-838) nosetter access strategy on <version> tag causes incorrect dirty check result

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-838?page=all ]
     
Sergey Koshcheyev closed NH-838:
--------------------------------

    Fix Version:     (was: LATER)
     Resolution: Incomplete

> 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