Hi,
in one case I tracked a ObjectModifiedException down to a problem with Optimistic
Locking against the database.
Setting the dirty attribute (of every field) to ignore disables this behaviour.
e.g: <sql type="integer" dirty="ignore" name="ID" />
This changes the SQL which tries to update the records.
It doesn't check anymore that the values of the record weren't changed by a different
transaction.
This check didn't work correctly in my case ( DATE fields, ORACLE 8.17).
Regards, Christoph
--
Diese E-Mail enth�lt vertrauliche und/oder rechtlich gesch�tzte Informationen. Wenn
Sie nicht der richtige Adressat sind oder diese E-Mail irrt�mlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das
unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the
intended recipient (or have received this e-mail in error) please notify the sender
immediately and destroy this e-mail. Any unauthorized copying, disclosure or
distribution of the material in this e-mail is strictly forbidden.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
