Adam wrote:

> If this occurs, you have two
> transactions trying to update the *same* record within product, which
> if the second attempts it from a transaction started before the first
> commits would cause a lock conflict.

It causes deadlock. My applications alert users about this, rollback
their transaction(s), and they can click on "Save" button again when
"coast is clear".

I still fail to see why would that be unsafe: AFAIU the data in database
remains consistent?

--
Milan Babuskov
http://swoes.blogspot.com/
http://www.flamerobin.org