You can have any number of timestamp columns, but only one of them can be set to autoupdate. As of 4.1 you are not limited to this being the 1st one in the table and CURRENT_TIMESTAMP, CURRENT_TIMESTAMP(), or NOW() can be used in the DEFAULT. Read
http://dev.mysql.com/doc/mysql/en/timestamp-4-1.html The DATETIME, DATE, and TIMESTAMP Types for MUCH more detail. -----Original Message----- From: Greg Whalin [mailto:[EMAIL PROTECTED] Sent: Thursday, June 09, 2005 2:54 PM To: Jeff Smelser Cc: mysql@lists.mysql.com Subject: Re: Seriously.. When are we going to get subqueries?! Jeff Smelser wrote: > On Thursday 09 June 2005 01:26 pm, George L. Sexton wrote: > > >>Another limitation in MySQL is that you can only have one timestamp column >>with a default of CURRENT_TIMESTAMP. >> > > > How many friggin times do I have to say that this is not an issue with 4.1 and > above? Which, BTW, is production mysql.. > > Why do you keep bringing this up? > > Jeff Are you sure? I don't see that from http://dev.mysql.com/doc/mysql/en/timestamp-4-1.html It seems that w/ > 4.1, you can specify any ONE timestamp col w/ default of CURRENT_TIMESTAMP. You are not limited to the 1st one, but still seems you are limited to a max of 1 timestamp. Or am I reading this wrong? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
