On 5/11/05, Bastian Balthazar Bux <[EMAIL PROTECTED]> wrote: > 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.
I'll mention here that postgresql also requires a dump/restore to upgrade from 7.x to 8.0. Additionally, while MySQL AB lists both 4.0 and 4.1 as Generally Available, 4.1 is the recommended release, and we should expect 5.0 production releases in about 1-2 months (I think their target is June). The MySQL folks have told me (at the recent conference) that there are no C API changes from 4.1 to 5.0. There is a minor change relating to the reconnect option for connections, but it seems unlikely to break anything. Bastian's ebuilds work well for both 4.1 and 5.0: https://bugs.gentoo.org/show_bug.cgi?id=83011 I think both 4.1 and 5.0 should be merged into the Portage tree. Both of Bastian's ebuilds for these versions will refuse to install if an earlier version is present. I think perhaps it would be better if they had a dependency specified to prevent Portage from even trying to merge, i.e. for the 5.0 build: DEPEND="!<dev-db/mysql-5" and for 4.1: DEPEND="!<dev-db/mysql-4.1" I'd still hard-mask mysql-5 for now, but I think it would be helpful to have it in the tree. 4.1 should be un-hard-masked but needs time in testing (~arch). Once it's completely unmasked, those who don't want it can mask it locally. (I am still using 4.0 in production servers.) BTW, to minimize downtime, you can upgrade like this: emerge --onlydeps =mysql-5.0.4_beta && \ emerge --buildpkg --nodeps =mysql-5.0.4_beta # dump data, shutdown server emerge --unmerge mysql && \ emerge --usepkg =mysql-5.0.4_beta # start server, reload data revdep-rebuild # should not be needed for 4.1 to 5.0 upgrade > Here the following applications run in a production environment with > mysql-4.1: I'll also add that mysql-python works fine with 4.1 and 5.0. -- Computer interfaces should never be made of meat. http://www.terrybisson.com/meat.html -- [email protected] mailing list
