Hibernate Version: 2.1.4

I hope I no one will be offended if I ask a general question. We have encountered a highly repeatable situation and I could use a little education as to how to best avoid it.

Imagine, if you will, two threads with identical activities and overlapping transactions:

1) Session a/Transaction a begin and load an Object X.
2) Session b/Transaction b begin and load the same Object.

3) Session a deletes Object X and Transaction A commits.
4) Session b deletes Object X and Transaction B commits. And...

An exception will occur because Session b cannot find the row.

(The text of the message will vary depending on whether batch updates are enabled but the indication is the same = Unexpected row count.)

Obviously the delete could first confirm the presence of the row but is there a better way?

Thanks

Have you heard about Isolation levels on you database?
Your transaction will currently run on "read commited" which is the default isolation afaik.

I would suggest that you let the database do the job for your problem.

You can find the something about that here:
http://www.hibernate.org/hib_docs/reference/en/html_single/#transactions-locking


a good description about isolation level (this is basicly database independend:
http://www.mssqlcity.com/Articles/General/TIL.htm

simon

Thanks Simon.

Wasn't aware that you could set the concurrency on a Txn by Txn basis...