Hi,
I am planning to use Database Level Managed Versioning to implement Optimistic Locking. ie: Will control version at the Database Level via Triggers. Now i need to genrate an Update Command which would look like

Update table
set col1 = x, col2 = y
where Primary_key = value
and version = value

Any Ideas how can i generate such a Update Command....


Regards

Prasanth

NHibernate has built-in optimistic locking, see the <version> element. I belive that it should also work if new version value is assigned by trigger... Only that, if trigger assigns a number different than NHibernate thinks should be, You must refresh object after save. Maybe NHibernate can be configured to do it automatically, I do not know.. (I'm just a newbie :-P )

Hey Thankz,
For some funny Reason <version> tag dosnt work if it is placed after a <property> tag. But works well when placed after the <id> Tag.


Also What i wanted was that the versin should not Update the version column. IS that Possible. If not is there any other way in which similar Could be achieved. As i might be using the Oracle inbuilt ORA_SCN Number to Maintain Versioning.

The NHibernate mapping schema demands that the tags in a mapping file follow a specified sequence, which is why <version> cannot follow a <property> tag.



Are you saying that you want to use NHibernate's versioning but don't want NHibernate to modify any version numbers? If so, then I can't see much point in using NHibernate's versioning at all. Can you provide some information as to why you want to do this?

What I am Looking for is updating the version Col Using Triggers. I am not planning to Update versions in The Business Logic. Thats why i want the Version not to update the version Col.

NHibernate manages the versioning for you behind the scenes.. you do not need the triggers

...which is fine as long as your NHibernate application is the only thing updating your database. Sometimes it's nice to have versioning controlled at the lowest possible level.

Symon.