Hi,

I've read Hibernate reference, but I'm still confused over this issue. Say I have many client machines running a software that I developed using Hibernate and all of them use the same database server.

What's the best way to avoid concurrency problems, such as one of the clients working with stale data because another one changed it?

If I use the .reconnect() approach (13.3.1 on the reference doc), does Hibernate guarantee that the data is not stale or do I have to use session.lock() (13.4 on the reference doc)?

Thanks for any pointers in this matter.

V

As long as you use versioned data, Hibernate will handle optimistic locking automatically.

The documentation covers this pretty well. Check out http://www.hibernate.org/hib_docs/reference/html/transactions.html#transactions-s3

>> does Hibernate guarantee that the data is not stale...
If you use session.disconnect()/reconnect() the data actually has a much higher chance of being stale. Therefore, if you use this approach, you should use session.lock() prior to attempting to update it to ensure that it has not changed.

The easiest plan of action is to utilize one of the versioning techniques outlined in the documentation.