This one time, at band camp, Neil Aggarwal said: NA>Bruce: NA> NA>I implemented the TimeStampable interface and I still get a NA>ModificationException when I try to update the object. NA> NA>Does it make a difference that I implemented the interface NA>in a superclass?
Without more detail it's tough to say what it is. But what I can suggest is that fields of type date, float and double can sometimes fail Castor's dirty check (which utilizes a .equals()). This can sometimes be narrowed down by employing the dirty="ignore" attribute in the <sql> element of the mapping descriptor. Oftentimes by going through this other problems may be found getting closer to a solution. Bruce NA>-- NA>Neil Aggarwal NA>JAMM Consulting, Inc. (972) 612-6056, http://www.JAMMConsulting.com NA>Custom Internet Development Websites, Ecommerce, Java, databases NA> NA>> Neil, NA>> NA>> There is no need for you to worry about the timestamp with regard NA>> to long transactions. Simply implement the TimeStampable interface NA>> (http://www.castor.org/javadoc/org/exolab/castor/jdo/TimeStampable.html) NA>> in the objects invovled in the long transaction. See the following NA>> for more information: NA>> NA>> http://www.castor.org/long-transact.html NA>> NA>> Bruce NA>> -- NA>> NA>> perl -e 'print NA>> unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");' NA>> NA>> ----------------------------------------------------------- NA>> If you wish to unsubscribe from this mailing, send mail to NA>> [EMAIL PROTECTED] with a subject of: NA>> unsubscribe castor-dev NA> NA>----------------------------------------------------------- NA>If you wish to unsubscribe from this mailing, send mail to NA>[EMAIL PROTECTED] with a subject of: NA> unsubscribe castor-dev NA> -- 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
