[nhibernate-issues] [JIRA] Updated: (NH-305) Database-managed version columns

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

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

Sergey Koshcheyev updated NH-305:
---------------------------------

    Fix Version: LATER
        Version: 1.2.0.Beta2

> Database-managed version columns
> --------------------------------
>
>          Key: NH-305
>          URL: http://jira.nhibernate.org/browse/NH-305
>      Project: NHibernate
>         Type: New Feature
>   Components: Core
>     Versions: 1.2.0.Beta2, beta-0.8.4
>     Reporter: Sergey Koshcheyev
>     Priority: Minor
>      Fix For: LATER

>
> NHibernate should be able to use database-managed version columns (timestamp on MySQL and SQL Server, xmin on PostgreSQL, etc.) This means querying the database for the version after an insert/update, and some care has to be taken to prevent possible race conditions (some other thread might modify the data between insert/update and version select).

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