Using Version/Timestamp

» Home » ActiveRecord » Documentation » ActiveRecord trunk Documentation » Advanced usage » Using Version/Timestamp

The NHibernate's Version and Timestamp feature can be used on Castle ActiveRecord as well. Those are used to detect changes from other processes/requests, avoiding a last-win situation.

When saving, NHibernate will make sure that the update will only succeed if the version/timestamp in the database match the version/timestamp on the object. If they are different, the changes will not be saved, and a StaleObjectException will be thrown.

Using Version

Version can be of the following types: Int64, Int32, Int16, Ticks, Timestamp, or TimeSpan.


[Version("customer_version")]
public Int32 Version
{
  get { return version; }
  set { version = value; }
}

Using Timestamp

Note that using [Timestamp] is equal to using [Version(Type="timestamp")]. Because of timestamp precision issues, [Version] is consider safer to use than [Timestamp]


[Timestamp("customer_timestamp")]
public Int32 Timestamp
{
  get { return ts; }
  set { ts = value; }
}

Home

Castle Stronghold

Table of contents

Using Version/Timestamp

Using Version

Using Timestamp