--- In [email protected], "Jeff Vroom" <[EMAIL PROTECTED]> wrote: > It is now trying > to do conflict detection on its own by comparing the previous version > with a version of the hibernate object it loads into that session. That > won't be transactionally correct unless you are using a strict isolation > level and Hibernate has its own versioning stuff which we should be > using instead.
Just an FYI, I have turned off all UPDATE conflict detection in FDS (<update-conflict-mode>NONE</update-conflict-mode>) in an attempt to get the "simple case" working. I am fine with using Hibernate's versioning for conflict detection. PW
