This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
The moose likes Object Relational Mapping and the fly likes Optimistic concurrency in hibernate using version/timestamp. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

JavaRanch » Java Forums » Databases » Object Relational Mapping
Bookmark "Optimistic concurrency in hibernate using version/timestamp." Watch "Optimistic concurrency in hibernate using version/timestamp." New topic

Optimistic concurrency in hibernate using version/timestamp.

sharath kumar reddy karnati

Joined: Jul 23, 2007
Posts: 5
Hi All,

I didn't understand how optimistic concurrency will work in hibernate?

As per my knowledge, we need to have either VERSION or TIMESTAMP column in persistence table which is mappend to hibernate.

Say we are having TIMESTAMP column then whenever we execute INSERT,UPDATE statement hibernate will modify TIMESTAMP column with system timestamp. When we try to update a row and that row timestamp is differenent from the existing row timestamp then it determines as stale data and it will through the error message.

Please correct me if I'm wrong and also provide some example too.

Thanks in advance.

Prakhyat madgunaki

Joined: Aug 07, 2007
Posts: 1
Below is a simple code, which will depict how optimistic locking/(concurrency control) will be done by hibernate.

// foo is an instance loaded by a previous Session
session = factory.openSession();
int oldVersion = foo.getVersion();
session.load( foo, foo.getKey() );

if ( oldVersion!=foo.getVersion )
throw new StaleObjectStateException();

Have you checked out Aspose?
subject: Optimistic concurrency in hibernate using version/timestamp.
It's not a secret anymore!