This one time, at band camp, Thomas Phan said:
TP>However, if I use MS SQL server, I passed the above error, then got
TP>"org.exolab.castor.jdo.ObjectModifiedException: Transaction aborted: Object
TP>of type esb.interfaces.RoleData with identity admin has been modified by a
TP>concurrent transaction" when Castor called store(). I'm sure that I was the
TP>only user who modified the data!
So the object was modified in one transaction and committed in a
second transaction. The second transaction must utilize db.update(
object ) in order to notify Castor that the object has changed so
that the commit of this transaction will persist the changes.
TP>When I use MySQL, this problem doesn't exist! Is this a well-known bug that
TP>needs special handling?
It seems odd that this would happen in one database and not another.
Have you changed the mapping descriptor or the code when moving
from database to another?
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
