Is there a way to get Hibernate to do optimistic locking on delete operations?

I've got optimistic locks on update, that's fine. I'd also like a delete operation to fail if the object being deleted has been updated since it was retrieved.

Or to put it another way: two threads T1 and T2 both read an Object O (at version 1). T1 does an update to O, incrementing its version to 2. T2 then deletes its O (the version 1 one) but this should then fail because version 1 no longer exists.

Is this one of those things that isn't considered useful/normal, or have I missed a switch or an XML attribute somewhere?

OK, no takers so far. So how about I suggest a possible solution?

I'm thinking that instead of calling Session.delete(Object object) I could instead call Session.delete(String query) with a query of something like:



I can then check the return value of delete(String query) and throw an exception to indicate that the underlying object has been changed if no rows were deleted.

Clearly an update-related optimistic lock using versioning could be done in exactly the same way, but Hibernate provides a facility to hide the version check away, and I'm just wondering if there's a similar facility for delete-related optimistic locks.