Managing Mutiple Transaction with Hibernate

anand_vishal · **Posted:** Wed Jul 09, 2008 9:37 am

I need to develop a process which involves a database table with 'n' number of records with 'm' number of user accessing the table.
Like for example Table contain records like Data1, Data2,Data3....,DataN
Users are User1, User2, ....UserN.

Now at some time User2 is trying to modify Data2 and at the same time User5 is deleting Data2.

So how can we handle such a situation via Hibernate? How can we maintain a lock on the table so that only one user can access a table when concurrent transaction is done?
And if we place this lock, how this lock can be flushed out after one transaction is complete?

My application is proposed to be on Java and Spring ?And I need a suggest a design for the same? Can anyone suggest anything?[b]

Cameron McKenzie · **Posted:** Wed Jul 09, 2008 5:05 pm

This is a standard, classical transaction management scenario. If you set your locking and transaction levels appropriately, you can alleviate any problems.

Just remember that Hibernate reads and writes data within the scope of a transaction. If the data is locked by one user, it won't be available until that user has completed their transaction. Then, another user may use the unlocked data.