If I turn optimistic locking off, it works as expected:
INFO: UPDATE Users SET name = ? WHERE id = ?
INFO: [bind: 1->name:'The Administrator', 2->id:200]
I did a little digging on Friday and it looks like the snapshot
doesn't contain the ID after the first commit which is what is causing
the "WHERE id IS NULL" to occur on the second commit (I think).
mrg
On Sun, Nov 7, 2010 at 7:21 PM, Andrus Adamchik <andru..bjectstyle.org> wrote:
> Very odd. Please file a Jira. Maybe we can reproduce it with our unit tests? So what is optimistically locked in this case?
>
> Andrus
This archive was generated by hypermail 2.0.0 : Mon Nov 08 2010 - 13:45:32 UTC