> In general lots of things could go wrong. PHP script is a good example. > If you use older versions of complex PHP-apps, upgrading mysql might not > be a very good idear. One of the things that might go wrong is the > charset-stuff. In MySQL 3-4.0 the char set on the server as one. In the > newer versions it is on table basis. This for example breaks older > versions of TYPO3.
I am currently using latin1. Could something break if I continue to set the default charset to latin1 ? I had that problem on a test environment a while ago...and had things solved then by setting the charset to latin1 as default. > And remember to follow the upgrade guide. Not doing so will b0rk your > server. I sure will :-) > If you can afford it, the safest approach IMO is to have an extra server > with the old MySQL-version on, that you keep alive, and then move your > databases one at a time. That is not a option for me as I don't control all the apps using the database server. But if charsets and library dependencies are the only things which could break my setup; and if I can avoid that by setting a default charset to "latin1" and by following the guide...the upgrade should be smooth I guess.... ? -- regards, Georges Toth -- [email protected] mailing list
