Does the use of the Version tag in the mapping for a Class for Optimistic Locking require any additional db feature (eg a sequence?), or is the version value or timestamp updated automatically by Hibernate?

Thanks,
Kevin

[This post does not relect the opinions of my Employer or it's clients in any way]

Hibernate automagically manages any version columns.

[This post does not relect the opinions of me, myself, or I :)]

Is there any way to use either the <version> or <timestamp> feature for Optimistic Locking, but to use a database trigger for updating the actual value in the database?

If I use a database trigger does this imply that I have to implement the optimistic locking logic myself (instead of using the version or timestamp feature)?

Thanks, Kevin Hooke

Its a problem, 'cos to figure out what value was generated by the trigger, Hibernate has to hit the db again, which is pretty much guaranteed to not perform well. So, I would say that this is not at all a good approach.

If I use the Timestamp feature in my mapping, where does the timestamp value come from when the column is updated on an update: from Hibernate (ie the app server) or from the database itself?