Thanks for these tips guys.
So, do you think the safest route is to do a full sql dump of my 4.0 dbs/tables, unmerge 4.0, emerge 4.1, and then load the dump file? That seems pretty scary to me, but the docs sound like that's the prefered route due to the character encoding changes.
Which approach did you use Jason? Has anyone just unamsked 4.1, installed it over a full, active 4.0 setup, done revdep-rebuild and had it all go fine? What problems have people had?
Also, anyone heard of any problems with 4.1 and PHP stuff like horde or pear?
thanks,
b
dormando wrote:
I would suggest you first read through this: http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html
Specifically, try the method described near the top (search for --new) about running MySQL 4.0 with 4.1's incompatible features enabled. If everything blows up, remove the option and restart your 4.0 server. Then don't upgrade :) If you're going to upgrade, carefully read the rest of that document first.
Sancho2k.net Lists wrote:
> And yes, you can emerge it easily. Either unmerge 4.0.x first and then > emerge 4.1.x, or just emerge it and watch it magically replace the old > version. > > Yes, there are library interface changes, so you will have problems with > broken reverse dependencies. revdep-rebuild works nicely for these cases. -- [email protected] mailing list
