Andreas,
I do not know about any issues with transactions, not for a single database.
Can you please tell us what you trying to do ? As to why it does work with
mySQL and does not with Oracle ... well, mySQL does not support full
transaction semantics with all of its database types.
Regards
Werner
On Thu, 16 Dec 2004 14:16:31 +0100, Andreas Vombach wrote:
>
>With castor 0.9.5.3 and MySQL works fine but when I change my DBMS to
>Oracle 9 I get the following exceptionwith an update commit:
>
>org.exolab.castor.jdo.ObjectModifiedException: Transaction aborted:
>Object of type persistence.worktime_monthly with identity 2 has been
>modified by a concurrent transaction (cache entry is different from
>database row)
>org.exolab.castor.jdo.ObjectModifiedException: Transaction aborted:
>Object of type persistence.worktime_monthly with identity 2 has been
>modified by a concurrent transaction (cache entry is different from
>database row)
> at org.exolab.castor.jdo.engine.SQLEngine.store(SQLEngine.java:880)
> at
>org.exolab.castor.persist.ClassMolder.store(ClassMolder.java:1609)
> at org.exolab.castor.persist.LockEngine.store(LockEngine.java:750)
> at
>org.exolab.castor.persist.TransactionContext.prepare(TransactionContext.java:1540)
> at
>org.exolab.castor.jdo.engine.DatabaseImpl.commit(DatabaseImpl.java:512)
>
>Are there any known problems with Oracle and transactions? Just reading
>works fine ...
>
>Cheers Andreas
>
>
>
>-----------------------------------------------------------
>If you wish to unsubscribe from this mailing, send mail to
>[EMAIL PROTECTED] with a subject of:
> unsubscribe castor-user
>
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
