Cleanup database on OConcurrentModificationException [moved]

[lvca]

This is Issue 278 moved from a Google Code project.
Added by 2011-03-23T20:27:53.000Z by sylvain....@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).

Original labels: Type-Defect, Priority-Medium, v1.0rc1

Original description

If a OConcurrentModificationException is thrown in a commit() call,
the database become in a bad state.

First, the database cache is not reseted: if I try to re-execute the
code and load the record again, the database give me back the old out
of synch record. Note really useful ;)

Second, the optimistic transaction is not killed, but not usable
anymore (old transactions entries always present). So I call
explicitly the rollback() method;

Here is a patch proposal, but I'm not sure it's the best solution.