hi,
We are tring to use managed version via hibernate 3.0 with sql server 2005. For now , the timestamp is used. As Hibernate in action said,
"Managed versioning relies on either a version number that is incremented or a
timestamp that is updated to the current time, every time an object is modified." (P169)
our question is that how the timestamp will be updated every time an object is modified ? Done by hibernate or by database? Indeed, we know that mysql can update the timestamp for us, but sql server seems not. I am not very sure about it so hope getting a help ,especially in the sql server 2005 scenario. If the timestamp can not be updated automatically by sql server or hibernate, does we need to use trigger to do that?


TIA


OrNot

Here is how I do it. Every object that I want to version (to prevent writing stale data) has an integer version property. A corresponding integer database row is also created. Hibernate takes care of everything else. If anyone tries to update an object with a version number lower than the current one in the db for that row, Hibernate throw an error.



If you really needed to know the time when data was modified, then that is a different kettle of fish.

You can do basically the same with a date/time:


I believe that you are not going to want a SQLServer timestamp -- just a date/time -- timestamp is managed by SQLServer.

Curtis ...