LAMP with ·dotmanila » default datetime value http://dotmanila.com/blog Linux Security, Apache Tuning, MySQL Optimization and PHP Programming Sun, 01 Aug 2010 01:54:55 +0000 en hourly 1 http://wordpress.org/?v=3.0.1 MySQL Default DATETIME Value – A Quick Rant http://dotmanila.com/blog/2009/11/mysql-default-datetime-value-a-quick-rant/ http://dotmanila.com/blog/2009/11/mysql-default-datetime-value-a-quick-rant/#comments Thu, 19 Nov 2009 16:39:22 +0000 jervin http://dotmanila.com/blog/?p=106 I was reviewing a year old code which I am adding a feature to. It so happened I came to a familiar issue about having two timestamp/datetime columns, one which should have the CURRENT_DATE / NOW() as default value and the other with an 'ON UPDATE CURENT_TIMESTAMP'. Examine the simple structure below:

CREATE TABLE `stories` (
`id` INT NOT NULL AUTO_INCREMENT PRIMARY KEY ,
`title` VARCHAR( 255 ) NOT NULL ,
`text` TEXT NOT NULL ,
`creationdate` DATETIME NOT NULL ,
`lastupdate` TIMESTAMP ON UPDATE CURRENT_TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP
) ENGINE = MYISAM

When you want to store stories, you would also want to record when it was originally created as well track the last time it was updated. The problem here is that adding a `DEFAULT NOW()` clause will not work for the `CREATE TABLE` query above as it is not supported. So when your insert a new story you will have to explicitly add a `NOW()` function for the `creationdate` row so it will reflect the current date as creation date. This should've been a simple schema functionality, turns out after more than a year MySQL seems to ignore for some reason.

Go on have yourself a read here http://bugs.mysql.com/bug.php?id=27645

How about you, how many times have you have to work around this from your application code?

]]> http://dotmanila.com/blog/2009/11/mysql-default-datetime-value-a-quick-rant/feed/ 0