The problem turned out to be a sequence which had recently been reset in
an external database.
But, I had forgotten about P6spy. So thanks for that reminder.
- laran
Armin Waibel wrote:
Hi Laran,
Laran Evans wrote:
I'm getting optimistic lock exceptions when saving an object. But, the
exception only comes up occasionally. It happens maybe 3 out of every 4
runs.
The object has 3 lists of objects, all of which are persisted as well.
Before saving the parent object all version numbers are null. After
saving
1) the parent object and all elements of two of the collections have a
version number of 1. 2) the elements of the third collection have version
numbers of 2.
Maybe OJB does perform the objects of the third collection twice (insert
+ update). Could you post the (pseudo) code of your test case? Did you
check the generated sql statements, e.g. via P6Spy (jar is shipped with
OJB)?
http://db.apache.org/ojb/docu/faq.html#traceProfileSQL
regards,
Armin
Can anyone spot from my simple description any potential optimistic
locking
issues?
Many thanks,
- laran
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
