Re: [eclipselink-users] Odd optimistic lock exception behavior

[jamesssss <jamesssss@xxxxxxxxx>]

The error is being caused because the executeUpdate is triggering a flush.
JPA requires that by default a flush() is executed before any query.  You
can set the flushMode to avoid this.

The lock exception occurs because you have changed an object in your
persistence context and it is out of date with the database. (probably
because you just deleted everything form Foo).




--
View this message in context: http://eclipse.1072660.n5.nabble.com/Odd-optimistic-lock-exception-behavior-tp1098p154080.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.