Rebuilding Or Repairing Tables Or Indexes - Oracle 5.0 Reference Manual

Table of Contents

Advertisement

downgrades. Also,
storage engines
These changes cause index rebuilding to be necessary:
• MySQL 5.1.24, 5.4.0 (Bug #27877)
Affects indexes that use the
contain
'ß'
original collations but introduced an incompatibility such that
which it previously compared different.
Affected tables can be detected by
(see Bug #40053).
A workaround for this issue is implemented as of MySQL 5.1.62, 5.5.21, and 5.6.5. The
workaround involves altering affected columns to use the
ucs2_general_mysql500_ci
utf8_general_ci
• MySQL 5.0.48, 5.1.23 (Bug #27562)
Affects indexes that use the
characters:
RIGHT SQUARE BRACKET,
Affected tables can be detected by
(see Bug #39585).
• MySQL 5.0.48, 5.1.21 (Bug #29461)
Affects indexes for columns that use any of these character sets: eucjpms, euc_kr, gb2312,
latin7, macce,
Affected tables can be detected by
(see Bug #39585).

2.19.4. Rebuilding or Repairing Tables or Indexes

This section describes how to rebuild a table. This can be necessitated by changes to MySQL such as
how data types are handled or changes to character set handling. For example, an error in a collation
might have been corrected, necessitating a table rebuild to update the indexes for character columns
that use the collation. (For examples, see
Be
Rebuilt".) It might also be that a table repair or upgrade should be done as indicated by a table
check operation such as that performed by
Methods for rebuilding a table include dumping and reloading it, or using
TABLE.

Rebuilding or Repairing Tables or Indexes

is not applicable to all storage engines. For details about which
CHECK TABLE
supports, see
CHECK TABLE
utf8_general_ci
LATIN SMALL LETTER SHARP S (German). The bug fix corrected an error in the
collations, which preserve the original pre-5.1.24 ordering of
and ucs2_general_ci.
ascii_general_ci
GRAVE ACCENT,
'`'
'~'
ujis
Note
If you are rebuilding tables because a different version of MySQL will not handle
them after a binary (in-place) upgrade or downgrade, you must use the dump-
and-reload method. Dump the tables before upgrading or downgrading using
your original version of MySQL. Then reload the tables after upgrading or
downgrading.
If you use the dump-and-reload method of rebuilding tables only for the purpose
of rebuilding indexes, you can perform the dump either before or after upgrading
or downgrading. Reloading still must be done afterward.
Section 13.7.2.3,
or
ucs2_general_ci
CHECK TABLE ... FOR UPGRADE
collation for columns that contain any of these
LEFT SQUARE BRACKET,
'['
TILDE
CHECK TABLE ... FOR UPGRADE
CHECK TABLE ... FOR UPGRADE
Section 2.19.3, "Checking Whether Tables or Indexes Must
TABLE, mysqlcheck, or mysql_upgrade.
CHECK
156
"CHECK TABLE
Syntax".
collation for columns that
compares equal to characters with
'ß'
as of MySQL 5.1.30, 5.4.0
utf8_general_mysql500_ci
REVERSE SOLIDUS,
'\'
as of MySQL 5.1.29, 5.4.0
as of MySQL 5.1.29, 5.4.0
ALTER TABLE
and
']'
or
REPAIR

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 5.0 and is the answer not in the manual?

Questions and answers

This manual is also suitable for:

Mysql 5.0

Table of Contents