hello guys.

i've finally starting using nhibernate in a professional project and i must say that i'm enjoying it a lot. However, there's a little problem with theway that the <version> element works.

According to the docs: "Version numbers may be of type Int64, Int32, Int16, Ticks, Timestamp, or TimeSpan (or their nullable counterparts in .NET 2.0). "

in my case, i'm using sql server and the version column is set to timestamp (SQL) which maps to a byte[] in C#. Now, in this case i might be able to change the type of column (for instance, to an int). However, what i'd really like to do is configure my <version> element so that it uses my sql server timestamp column for concurrency control. is this possible? any advices on how to achieve this?

Using a DB generated value for concurrency control through <version> is not supported. There may be ways to use it for 'manual' concurrency control--see the more recent messages on this thread.

hum...damn. this sucks. most of the existing databases with which i have to work use a timestamp column for concurrency control.

so, are there any workarounds for this? or are you just using ints for concurrency?

I just use ints, which unfortunately means that I need to do manual increments from the DB side.

As for a workaround: did you check out the link I provided above (http://forum.hibernate.org/viewtopic.php?t=962174)? It's not a complete solution, but it is a start...

hello.

hum...i was under the assumption that nhibernate will automatically update the integer, though i can be wrong. am i wrong?

thanks again.

You are right, sorry, I was confusing. What I meant is that when I make updates directly via SQL and stored procedures, I have to include version updates manually.

hello again.
oh, ok. got it:)

thanks for your help.

The idea was already published on CodeProject. Here is a link:
http://www.codeproject.com/useritems/Op ... xTable.asp
Hopefully you can found the useful suggestion.