4 Replies Latest reply on Oct 4, 2002 6:16 AM by dragos popa

    MySQL TIMESTAMP autoupdates itself during commandline update

    Jason Uithol Newbie

      Hi all,

      This post is quite lengthy and I apologise for it. I am concerned about using the TIMESTAMP datatype in MySQL and was wanting a few questions answered about it.


      The TIMESTAMP datatype of MySQL will update itself to the current date/time when a normal INSERT/UPDATE statement is made to it from any boring old connection e.g. the mysql monitor.

      NOTE: This only happens under two conditions

      (a) The INSERT/UPDATE statement is not explicity providing a value for that column.

      (b) It only happens to the _first_ TIMESTAMP column in the table ! Any other TIMESTAMP columns in the table are left alone ?!?!?!? Weird.

      Seeing this in action, I figured I'd better use java.util.Date, since in JBossCMP it maps the table type as the DATETIME datatype.

      However, when Jboss generates the new tables, it STILL uses TIMESTAMP. I notice that the mapping states that the mapped JDBC type is called TIMESTAMP.

      Has anyone else had this strange mapping behaviour happen to them ?

      Asumming that I am stuck with TIMESTAMP ( it seems from the Forums that other people are happy with it ... )

      - has anyone had any problems with the TIMESTAMP datatype updating itself ? I see from the debug logs when jboss is in action that the SQL statements cover every field, so in theory an explicit value is being provided for the TIMESTAMP field, so MySQL won't autoupdate it.

      Are there any cases when Jboss won't provide such a comprehensive INSERT/UPDATE statement ?


      Any advice would be appreciated.