Hi, TIMESTAMP has a valid range of only '1970-01-01 00:00:01' UTC to '2038-01-09 03:14:07'. This makes it not a good datatype for new systems, since 2038 is actually not so far away...
The important difference between DATETIME and TIMESTAMP is that TIMESTAMP columns (in MySql) offers automatic initialization and updating. The rules for this are not easy: (http://dev.mysql.com/doc/refman/5.1/en/timestamp.html) I noticed that the Table Prototype definition does not include the default clause, which is what you need to change how timestamp columns work. Does this mean that timestamp columns will always be updated as records are changed and inserted? Or that this functionality will be dropped so that timestamp columns will work like DATETIME columns? Erik Wetterberg On Tue, Aug 12, 2008 at 9:55 AM, Roy Lyseng <[EMAIL PROTECTED]> wrote: > > > Brian Aker wrote: >> >> Hi! >> >> On Aug 12, 2008, at 12:28 AM, Roy Lyseng wrote: >> >>> why do you need both TIMESTAMP and DATETIME? >> >>> TEXT should be named CLOB to be aligned with SQL standard... >> >> I am up for whatever folks want here. TEXT has always been the MySQL type. >> I do not mind using the standard type name (or aliasing it). >> > > If there is a standard, why not use it? Especially one that is so > comprehensive and consistent as the SQL standard (for most parts) :) > > Roy > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
