Revert to MySQL 4.1 from 5 -- should I?

[orty]

I'm about to migrate a bunch of sites from an old server to a new fancy one. My old server is a CentOS 4.5, Apache 1.4, PHP4, MySQL 4.1 box. The new one was setup with Apache 2.x, PHP5, MySQL 5, and CentOS 5.1. I'm not too worried about PHP 5 and apache 2, but I don't know a thing about MySQL5 -- how well does it work with older applications?

How do I go about downgrading if I feel the need. Has anybody had issues with just throwing a bunch of sites at MySQL 5.x? I know I'll need to enable old-style passwords, but I just wanted to see if there were any other gotchas out there.

-jake

[cPanelDavidG]

I'm about to migrate a bunch of sites from an old server to a new fancy one. My old server is a CentOS 4.5, Apache 1.4, PHP4, MySQL 4.1 box. The new one was setup with Apache 2.x, PHP5, MySQL 5, and CentOS 5.1. I'm not too worried about PHP 5 and apache 2, but I don't know a thing about MySQL5 -- how well does it work with older applications?

How do I go about downgrading if I feel the need. Has anybody had issues with just throwing a bunch of sites at MySQL 5.x? I know I'll need to enable old-style passwords, but I just wanted to see if there were any other gotchas out there.

-jake

MySQL 5 will not break applications that work on MySQL 4.1. However, PHP 5 is more likely to break a few PHP applications that are older and not well maintained.

[orty]

MySQL 5 will not break applications that work on MySQL 4.1. However, PHP 5 is more likely to break a few PHP applications that are older and not well maintained.

In my account audit, I only found one app that wasn't certified for PHP 5.x use, as most of my accounts, if they have any PHP stuff, are using recent versions of Drupal and Wordpress that have been PHP 5 ready for a long time. I plan on transferring over my questionable accounts first, test them on the new server w/out changing DNS over to the new server, and making sure they work before I transfer the live, fully functional, site.

[pjman]

Is there a quick way to do an account audit for PHP 4 to PHP 5 sites?

My server is PHP 4 now and I'm upgrading to PHP 5 in 2 weeks. It sure would be nice to know what will break prior to the upgrade.

[kemis]

pjman:

I'm debating switching to PHP5 right now. How did your migration go? Did you get any answers regarding a quick way to audit sites?

Matt

[pjman]

I made PHP 4 the default. On each site I just placed the HTTAccess handler in the directory I wished to test PHP 5 on.

It worked great! I was able to test individual directories little by little before switching whole sites over to PHP 5.

In the end, I just had problems on one of my ten sites because it requires an old module that doesn't support PHP 5. I added the new version of the module (PDFlib) and I'm slowly switching it over to work on PHP 5.

I'll save the MYSQL upgrade to 5 until next summer.

[forlinuxsupport]

Hey

You can run php 4 and 5 side by side (so best of both worlds)

Just set it so the one you want ".php" files to use as php version 4 and then ".php5" to use version 5.

Makes life a bit easier as you can update sites one at a time to use the new version (namely 5) - and troubleshoot as you go.

With regards to MySQL 5 - don't be scared - MySQL 5 is pretty good (and its now the default in cpanel anyway) - so update it now.

Cheers
Andy