Checking Whether Tables Or Indexes Must Be Rebuilt - Oracle 5.0 Reference Manual

4. Stop the newer MySQL server and restart the older one.
5. Reload the dump file into the older server. Your tables should be accessible.
It might also be the case that system tables in the
downgrading introduces some loss of functionality or requires some adjustments. Here are some
examples:
• Trigger creation requires the
TRIGGER
need to give the
• Triggers were added in MySQL 5.0, so if you downgrade from 5.0 to 4.1, you cannot use triggers at
all.
• The
mysql.proc.comment
downgrade from 5.5 to 5.1, this table is seen as corrupt and in need of repair. To workaround this
problem, execute
2.19.2.1. Downgrading to MySQL 4.1
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
[304]
routines
Database Backup
MySQL 4.1 does not support views. If your databases contain views, remove them with
before using mysqldump. (See
After downgrading from MySQL 5.0, you may see the following information in the
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
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 >
3. Stop the MySQL server.
4. Start MySQL 4.1 with the
5. Run
mysql mysql <
6. Run
mysqladmin

2.19.3. Checking Whether Tables or Indexes Must Be Rebuilt

A binary upgrade or downgrade is one that installs one version of MySQL "in place" over an existing
version, without dumping and reloading tables:

Checking Whether Tables or Indexes Must Be Rebuilt

TRIGGER
privilege and is required instead. If you downgrade from MySQL 5.1 to 5.0, you will
SUPER
privilege to those accounts that had the
SUPER
column definition changed between MySQL 5.1 and 5.5. After a
mysql_upgrade
and
--skip-triggers
Program".)
Section 13.1.19,
--skip-grant-tables
/tmp/mysql.dump.
flush-privileges.
database have changed and that
mysql
privilege as of MySQL 5.1. In MySQL 5.0, there is no
from the version of MySQL to which you downgraded.
mysqldump
[305] options. (See
"DROP VIEW
[420]
154
privilege in 5.1.
TRIGGER
by using the
Section 4.5.4, "mysqldump
Syntax".)
mysql.err
table to a format that
mysql.user
/tmp/mysql.dump.
option.
--skip-
— A
DROP VIEW
file: