Ben Munat wrote: > 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,
If you love your data dump and reload in any switch between 4.0 - 4.1 - 5.0 . The only scenario where it's not needed is for tables that have no textual fields inside. Quite everithing nowadays work with mysql-4.1 . You may want to compile net-libs/libwww without "mysql" use flag or go to bug 85783 In case you are using MyODBC rename ebuild to the latest version and go with it. Here the following applications run in a production environment with mysql-4.1: Horde + Imp Postfix Courier Samba php5 -> mysqli -- [email protected] mailing list
