Adam Esterline wrote:
> Have you tried the lazy load feature on the relationship fields?
Thanks for the suggestion Adam, I have tried this, as well as different
transaction levels (db.lock() as well as in the mapping). I still get
the error, and in addition to this I have discovered it is ONLY employee
id of 50 which causes the problem.
In any case, it is clearly a bug in JDO as there are no other
transactions in progress anywhere, either within the Castor app or via
JDBC/ODBC/etc elsewhere that could be changing this record in mid
transaction. Therefore, somehow the transaction is interfering with
itself in some bizarre way.
I would welcome any other hints as to what the nature of the problem is
and how it can be avoided. I am tempted to manually delete the offending
record from the database and pray that this never happens again, but
that wouldn't be a very satisfactory outcome. I would rather help to
understand what is wrong with JDO!
Patrick
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
