All, following some quite similar threads on the mailing list recently re: ObjectModifiedExceptions, I felt it a good idea to explain a recent enhancement in detail to the user community.
As stated in src/etc/CHANGELOG JDO: Fixed bug 1462 using contribution from Christoph Ernst [EMAIL PROTECTED] Fixes a problem with SQL type conversions between java.sql.Timestamp and java.util.Date and vice versa. Additionally, this fixes a couple of problems with the use of various resource entries (jdo.store, etc.) and generally improved code quality by removing unused import statements and local variables. (Werner - 20040206) the current release of Castor includes a patch/fix for bug 1462 documented at http://bugzilla.exolab.org/show_bug.cgi?id=1462. In the past, many of you have been advised to deal with these ObjectModifiedExceptions by using dirty="ignore" for those attributes that caused the exception to show up. In general, the problem applied to SQL fields of type java.sql.Timestamp only, or where a class member of type java.util.Date was mapped to a SQL column of type java.sql.Timestamp. The patch provided takes care of this problem in that a conversion problem wit the nanosecond part of java.sql.Timestamp has been addressed and fixed. As a result, it shall not be necessary anymore to use the dirty="ignore" instruction for the fields in question ... if - and that ONLY if - you happen to use a RDBMS that allows you to store fractions of a second with your datetime et alias values. For RDBMS that do not offer this feature (like e.g. mySQL), there's still an issue out there what will be addressed through a separate bug (1533, as shown in the dependency list of bug 1462). I hope this explains some of the issues that have been addressed, and makes things a little bit clearer and easier for you. Regards Werner ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
