At 19:14 +0100 14/4/06, Philippe Poelvoorde wrote:
Have a serious look at :
http://dev.mysql.com/doc/refman/4.1/en/upgrading-from-3-23.html
http://dev.mysql.com/doc/refman/4.1/en/upgrading-from-4-0.html
http://dev.mysql.com/doc/refman/5.0/en/upgrading-from-4-1.html
There is many things likely
At 19:14 +0100 14/4/06, Philippe Poelvoorde wrote:
Have a serious look at :
http://dev.mysql.com/doc/refman/4.1/en/upgrading-from-3-23.html
http://dev.mysql.com/doc/refman/4.1/en/upgrading-from-4-0.html
http://dev.mysql.com/doc/refman/5.0/en/upgrading-from-4-1.html
I will definitely do this.
At 8:32 -0700 13/4/06, paul rivers wrote:
Going from 3 to 5 can break a number of important things. For example, join
syntax semantics and precedence rules have changed since 3, and it is
certainly possible this could break your code in important and dramatic
ways.
You should plan on
Hi,
Yeah - I think the playground is unlikely to happen. They certainly
haven't said anything about providing such a facility.
If they don't give a test machine, or don't provide a smooth migration
(like installing a new server, and keeping the old one running 3.23),
you should consider
Chris Sansom wrote:
Our web host is currently running MySQL 3.23.something, but we're
shortly to be upgraded to MySQL 5.
Can I be sure that this is absolutely backwards compatible? Are there
any nastinesses lurking that I should know about that might cause my
databases to collapse in a heap?
At 11:56 +0200 13/4/06, Barry wrote:
Make a real downgradeable SQL Dump (without collations n stuff) and
have it saved.
Upgrade to MySQL 5.x and execute that sql dump.
Be warned that for example CONCAT behaves in a different way than in 3.x.
If you have PHP scripts with some functions in
Sansom [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 13, 2006 3:54 AM
To: Barry; mysql@lists.mysql.com
Subject: Re: MySQL 3 to 5 upgrade
At 11:56 +0200 13/4/06, Barry wrote:
Make a real downgradeable SQL Dump (without collations n stuff) and
have it saved.
Upgrade to MySQL 5.x and execute that sql