mazur <[EMAIL PROTECTED]> wrote:
> Anyone know if there is a way to defeat the new format for the
> timestamp that appears in 4.1 alpha?
>
> I upgraded a MySQL install on a development box that holds a copy of
> our production data. I quickly saw that the timestamp format was
> changed from:
>
> 20030520124559 , to:
> 2003-05-20 12:45:59
>
> For better or worse (worse at the moment), I have a large app that is
> (unfortunately) dependent on the old format...blows up in many places
> without it actually. Anyone else in the same boat? Any thoughts
> about this dilemna, other than to say the app should not have been
> built to be dependent on the old format? :-)
Use timestamp_column+0 :
http://www.mysql.com/doc/en/Prepare-upgrade-4.0-4.1.html
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Victoria Reznichenko
/ /|_/ / // /\ \/ /_/ / /__ [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]
