ERROR: WordPress 2.8 requires MySQL 4.0.0 or higher

Client API version 4.0.12

what you pasted isnt the output of the version of your install. While that may be the version you are using — that particular output isnt reliable, since thats not it.

this will get your mysql Version from within mysql:

<?php
$link = mysql_connect('host', 'username', 'passwd');
if (!$link) {
    die('Could not connect: ' . mysql_error());
}

echo 'Connected successfully </br />';

$whoo=mysql_query("select version() as ve");
$getit=mysql_fetch_object($whoo);
echo "you are running MySQL ". $getit->ve;
mysql_close($link);
?>

Also note WordPress Version 2.9 will require MySQL 4.1.2 or greater.

Thankyou for the clarification

Indeed, the output says

Connected successfully
you are running MySQL 3.23.54-log

I have sent this to the server admin tech guy for comment. Do you think it is their responsibility to sort this out? I shouldn’t have to change any code in the way WordPress connects to these guys database setup should I?

BTW, this is what the tech guy says:

“…I believe the problem my be in the way you are connecting to MySQL. I had a similar problem with phpmyedit and had to hand code the connection code. As it is a shared database you have to make sure the connection code specifies the database name as it tries to connect. Cannot remember exactly but was in there somewhere.”

Go find your tech guy and then hit him with a stick.

The version of the database server has nothing to do with how you connect to it. It’s running a very old and outdated version of mySQL. The only fix is to upgrade it. Preferably to version 5 or higher.

I hear ya. But I wont hit him with a stick. He’s a good guy. He just needs to update the MySQL.
Peace

Okay, your call. I find that hitting people with a stick is often the only way they’ll learn. ??

Otto42

Totally disagree with the use of a big stick. That is completely outrageous. Is there a shortage of cod near you? – if so – use haddock.

I wouldn’t waste it, our blue cod here in NZ is too nice…
Case closed, I’m going to change host.

Andy…

That’s a very good decision.

BTW… from what you said about the techie guy, it is clear that running the upgrade is beyond him. It’s quite involved… best done in stages – with a series of tests. Also requires knowing shell command line. Although I have been told there is a way to do it using phpMyAdmin.

Given his complete lack of knowledge. Not sure he wold have handled this – assuming mySQL 5 is ready to go on your server:

Upgrading from MySQL 3.23 to MySQL 5, to avoid compatibility issues it is best to upgrade to MySQL 4.0 first as a stepping stone.

Bear in mind that after you have upgraded, you should use the files and directories associcated with the new version of MySQL. If, for example, you move from 3.23 to 5.0, rather than using /usr/bin/mysql you would need to use /opt/mysql-5.0/bin/mysql.

Overview

The upgrade process in outline is broadly the same across versions (file and directory paths do vary though, so take care).

1. Stop the old MySQL (edit rc.conf and reboot)
2. Backup (copy the directory)
3. Rename the data directory
4. Start the new MySQL (edit rc.conf and reboot)
5. Run the new version’s upgrade commands
6. Confirm that the database is functioning properly
7. Remove the backup

Step by step from 3.23 -> 4.0

The first thing you will need to do is backup the existing data.

Disable the existing MySQL installation. Open the /usr/local/etc/rc.conf file, and locate the following line:

mysql_enable=”YES”

Change it to read:

mysql_enable=”NO”

Reboot server. MySQL is now not currently running, so the data on disc is in a consistent state.

Copy the database directory:

cp -a /usr/local/var/lib/mysql /usr/local/var/lib/mysql.v3.backup

Move the database directory:

mv /usr/local/var/lib/mysql /usr/local/var/lib/mysql-4.0

Change /usr/local/etc/rc.conf to read:

mysql_enable=”YES”
mysql_version=”4.0″

Once you’ve made this change, reboot the server. You’ll now be running MySQL 4.0 rather than the original 3.23 version.

There are still some changes to be made to enable the system to work correctly.

Firstly you will need to upgrade the MySQL privilege table. This is achieved by typing at the shell:

/opt/mysql-4.0/bin/mysql_fix_privilege_tables <password>

Substitute your MySQL administrator’s password for <password>.

Some existing databases may also need to be upgraded to new table types. You can achieve this by using the command:

/opt/mysql-4.0/bin/mysql_convert_table_format <databasename>

Running this command for each of your databases will upgrade them to the new table format.

Once you are happy that MySQL 4 is working correctly you can remove the backed up data (unless you are moving to MySQL 5 by way of MySQL 4, in which case you may wish to keep the backups until you have completed the entire process).

rm -rf /usr/local/var/lib/mysql.v3.backup

4.1 and beyond

The upgrade from MYSQL 4.0 to MySQL 4.1 and above follows the same basic outline , just the file/directory paths vary.

E.g. /opt/mysql-4.0/bin/ becomes /opt/mysql-4.1/bin/ or /usr/local/var/lib/mysql-4.0/ becomes /usr/local/var/lib/mysql-5.0/.

So from MySQL 4.0 to MySQL 5.0:

Edit /usr/local/etc/rc.conf:

mysql_enable=”YES”

to:

mysql_enable=”NO”

Reboot:

reboot server

Backup:

cp -a /usr/local/var/lib/mysql-4.0 /usr/local/var/lib/mysql.v4.0.backup

Rename:

mv /usr/local/var/lib/mysql-4.0 /usr/local/var/lib/mysql-5.0

Edit /usr/local/etc/rc.conf:

mysql_enable=”YES”
mysql_version=”5.0″

Reboot:

rebootv server

Run upgrade command

/opt/mysql-5.0/bin/mysql_upgrade –datadir=/usr/local/var/lib/mysql-5.0 <password>

Once you are happy that MySQL 5 is working correctly:

rm -rf /usr/local/var/lib/mysql.v4.0.backup

Thankyou for the clarification

youre welcome, good luck..