This documentation is for an older version. If you're using the most current version, select the documentation for that version with the version switch in the upper right corner of the online documentation, or by downloading a newer PDF or EPUB file. Changes Affecting Downgrades from MySQL 5.0

Before downgrading from MySQL 5.0, review the changes described in this section. Some changes may require action before or after downgrading.

MySQL 4.1 does not support stored routines or triggers. If your databases contain stored routines or triggers, prevent them from being dumped when you use mysqldump by using the --skip-routines and --skip-triggers options. (See Section 4.5.4, “mysqldump — A Database Backup Program”.)

MySQL 4.1 does not support views. If your databases contain views, remove them with DROP VIEW before using mysqldump. (See Section 13.1.19, “DROP VIEW Syntax”.)

After downgrading from MySQL 5.0, you may see the following information in the mysql.err file:

Incorrect information in file: './mysql/user.frm'

In this case, you can do the following:

  1. Start MySQL 5.0.4 (or newer).

  2. Run mysql_fix_privilege_tables, which will change the mysql.user table to a format that both MySQL 4.1 and 5.0 can use.

  3. Stop the MySQL server.

  4. Start MySQL 4.1.

If the preceding procedure fails, you should be able to do the following instead:

  1. Start MySQL 5.0.4 (or newer).

  2. Run mysqldump --opt --add-drop-table mysql > /tmp/mysql.dump.

  3. Stop the MySQL server.

  4. Start MySQL 4.1 with the --skip-grant-tables option.

  5. Run mysql mysql < /tmp/mysql.dump.

  6. Run mysqladmin flush-privileges.