I dont really know but... Are you really sure TIMESTAMP is the SQL type you want and not DATETIME. TIMESTAMP has sub-second resolution and DATETIME second resolution. It might be possible that Java is tracking sub-seconds and therefore sees these columns as needing updating. The data might not be expressed as subseconds because java.lang.Date only has second resolution too, but that might not stop CMP tracking the fact and marking the object fields dirty.
I believe there to be other magic properties of the SQL type TIMESTAMP that simply dont apply to DATETIME. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875745#3875745 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875745 ------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
