DALive Editor <[EMAIL PROTECTED]> wrote: > > I just upgraded my MySQL to distribution version 4.0.17 up from 4.0.15 > (i think). I read in the readme file i think it was that the mechanics > or output of the timestamp column had changed. I had grown to like that > column type. What's the best way to handle this change? Espially > considering I have alot of data already in place. I read something about > the use of '+0': i haven't really understood that. >
Format of TIMESTAMP column was changed in version 4.1.0. In version 4.0.17 you can get new TIMESTAMP format if you run MySQL server with --new option. Using +0 you get the same format like version 4.0 does: mysql> select mydate+0 from test; +----------------+ | mydate+0 | +----------------+ | 20040209110608 | +----------------+ 1 row in set (0.00 sec) mysql> select mydate from test; +---------------------+ | mydate | +---------------------+ | 2004-02-09 11:06:08 | +---------------------+ 1 row in set (0.00 sec) -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
