Hello group,

I'm developing a reservation system and want to use hibernate for data access. The system should issue a seat number when someone reservates one. First the database is checked on a 'available' flag in a certain table. When the seat is still available it must be reserved (by setting the flag available to false).

The system makes use of a single database and two applications. Each application must be able to handle reservations. It could be that the two applications try to reservate a seat number at the same time. They both check if the available flag is set to true, and then they both set it to false. Both applications return with a valid reservation and two different persons are assigned to the same seat. How can I prevent this with hibernate? I dont want to lock a table for a whole transaction.

Thanks in advance.
Dee.

Did you checked this?
http://www.hibernate.org/hib_docs/v3/re ... ns-locking

Also take a look at optimistic concurrency control.

http://www.hibernate.org/hib_docs/v3/reference/en/html/transactions.html#transactions-optimistic