http://gusiev.com/2009/04/update-and-create-timestamps-with-mysql/ How to make your web application Fri, 30 Jul 2010 11:55:48 +0000 http://wordpress.org/?v=2.5 http://gusiev.com/2009/04/update-and-create-timestamps-with-mysql/#comment-391 Hung Romo Wed, 14 Jul 2010 19:16:00 +0000 http://gusiev.com/?p=16#comment-391 Your weblog is incredibly helpful,I need to connect with u,could i sent e-mail to you? http://gusiev.com/2009/04/update-and-create-timestamps-with-mysql/#comment-130 ahjan Fri, 22 Jan 2010 09:29:16 +0000 http://gusiev.com/?p=16#comment-130 hi! for the "insert into test_table(stamp_created, stamp_updated) values(null, null); " statement.. how would u write it in php codings so that whenever a new data is created, it will automatically include the date created.. bcux right now i tried writing the insert in mysql codings but it only shows null null for other column info.. only the date modified n created are updated.. as im using a webpage to add data it doesn shows the created time.. rather it shows the "0000-00-00 00:00:00". only my updated column can b updated.. pls help thks! http://gusiev.com/2009/04/update-and-create-timestamps-with-mysql/#comment-122 Ped Wed, 16 Dec 2009 10:09:40 +0000 http://gusiev.com/?p=16#comment-122 I don't get it. If you already have a "workaround" which does force you to insert null, why don't you insert NOW() instead of null? With trigger workaround you gain the advantage to not mention "stamp_created" at all, so I can see a point there, although I personally refrain from such trigger usage, and I rather add NOW() into my inserts, which is IMHO much better then using "null" hack described here. Because honestly, this looks more like a bug to me. If you want 0000-00-00 as default, why don't you get it? I would be not shocked if MySQL would decide to change this behaviour later in future and "fix" it. (although I would rather welcome to have 2+ columns default NOW fix :) ) ) ]]> http://gusiev.com/2009/04/update-and-create-timestamps-with-mysql/#comment-117 sl fuqua Wed, 25 Nov 2009 22:01:41 +0000 http://gusiev.com/?p=16#comment-117 It's crazy to have to do this. With dynamic websites, blogs, and such, it would seem obviously intrinsic that the original creation date should be maintained automatically somehow. Oh the naivety of the `nub` :). Thanks for saving me several hours work figuring this out. Regards, sl sl ]]> http://gusiev.com/2009/04/update-and-create-timestamps-with-mysql/#comment-113 Samo Wed, 18 Nov 2009 09:38:21 +0000 http://gusiev.com/?p=16#comment-113 thnx Bogdan, good trick http://gusiev.com/2009/04/update-and-create-timestamps-with-mysql/#comment-111 Mehedi Hasan Thu, 12 Nov 2009 09:44:35 +0000 http://gusiev.com/?p=16#comment-111 thanks a lot for the great tips... http://gusiev.com/2009/04/update-and-create-timestamps-with-mysql/#comment-65 Bogdan Gusiev Thu, 18 Jun 2009 20:00:19 +0000 http://gusiev.com/?p=16#comment-65 I was doing the same experiments that you mentioned in your blog. The trick above is the only one way to have both timestamps in current MySQL version. http://gusiev.com/2009/04/update-and-create-timestamps-with-mysql/#comment-64 Red Five Thu, 18 Jun 2009 19:01:58 +0000 http://gusiev.com/?p=16#comment-64 Oops, misread the default value thing. I just tried it, and by default it'll insert a timestamp value of '0000-00-00 00:00:00'. http://gusiev.com/2009/04/update-and-create-timestamps-with-mysql/#comment-63 Red Five Thu, 18 Jun 2009 18:58:22 +0000 http://gusiev.com/?p=16#comment-63 There's a simpler way: simply make your stamp_updated column first, and set its "on update" attribute to current_timestamp, with no default value. Then follow with your stamp_created column, and set nothing for default value or "on update". Timestamp values default to the current timestamp, according to http://www.haidongji.com/2009/01/04/interesting-things-about-timestamp-data-type-in-mysql/. http://www.haidongji.com/2009/01/04/interesting-things-about-timestamp-data-type-in-mysql/. ]]> http://gusiev.com/2009/04/update-and-create-timestamps-with-mysql/#comment-62 Andy Wed, 17 Jun 2009 22:54:42 +0000 http://gusiev.com/?p=16#comment-62 "Note that it is necessary to enter nulls into both columns during ‘insert’:" Actually, you only need the null for the stamp_created as the stamp_updated will get updated automatically. mysql> insert into test_table(stamp_created) values(NULL); Query OK, 1 row affected (0.00 sec) mysql> select * from test_table; +----+---------------------+---------------------+ | id | stamp_created | stamp_updated | +----+---------------------+---------------------+ | 5 | 2009-06-17 15:54:18 | 2009-06-17 15:54:18 | +----+---------------------+---------------------+ Query OK, 1 row affected (0.00 sec) mysql> select * from test_table; +—-+———————+———————+
| id | stamp_created | stamp_updated |
+—-+———————+———————+
| 5 | 2009-06-17 15:54:18 | 2009-06-17 15:54:18 |
+—-+———————+———————+ ]]>