Oracle 5.0 Reference Manual page 1188

If
USE_FRM
so, it performs the upgrade, following the same rules as
Section 13.7.2.3,
without
USE_FRM
By default, the server writes
replication slaves. To suppress logging, use the optional
LOCAL.
You may be able to increase
Section 8.3.2.4, "Speed of
13.7.2.7.
RESTORE TABLE
RESTORE TABLE
RESTORE TABLE
directory should be specified as a full path name.
Existing tables are not overwritten; if you try to restore over an existing table, an error occurs. Just as
for
BACKUP
replicated from master to slave.
Table Maintenance Statements
in the unavailable to the repair process, which can have deleterious
.MYI
consequences:
• The current
AUTO_INCREMENT
• The link to deleted records in the table is lost, which means that free space
for deleted records will remain unoccupied thereafter.
• The header indicates whether the table is compressed. If the server
.MYI
ignores this information, it cannot tell that a table is compressed and repair
can cause change or loss of table contents. This means that
not be used with compressed tables. That should not be necessary, anyway:
Compressed tables are read only, so they should not become corrupt.
Caution
As of MySQL 5.0.62, if you use
different version of the MySQL server than the one you are currently running,
REPAIR TABLE
returned by
REPAIR TABLE
and a
Msg_text
Prior to MySQL 5.0.62, do not use
different version of the MySQL server. Doing so risks the loss of all rows in the
table. It is particularly dangerous to use
message:
Table upgrade required. Please do
"REPAIR TABLE `tbl_name`" to fix it!
is not used,
REPAIR TABLE
"CHECK TABLE Syntax", for more information. As of MySQL 5.0.62,
upgrades the
.frm
REPAIR TABLE
Important
In the event that a table on the master becomes corrupted and you run
on it, any resulting changes to the original table are not propagated to
TABLE
slaves.
REPAIR TABLE
REPAIR TABLE
Syntax
tbl_name [, tbl_name] ... FROM '/path/to/backup/directory'
Note
This statement is deprecated and is removed in MySQL 5.5.
restores the table or tables from a backup that was made with
TABLE, RESTORE TABLE
value is lost.
USE_FRM
will not attempt to repair the table. In this case, the result set
contains a line with a
value of
Failed repairing incompatible .FRM
USE_FRM
checks the table to see whether an upgrade is required. If
CHECK TABLE ... FOR
file to the current version.
statements to the binary log so that they replicate to
NO_WRITE_TO_BINLOG
performance by setting certain system variables. See
Statements".
currently works only for
1168
for a table that was created by a
value of
Msg_type
if your table was created by a
after the server returns this
USE_FRM
BACKUP
tables. Restored tables are not
MyISAM
should
USE_FRM
error
file.
UPGRADE. See
REPAIR TABLE
keyword or its alias
REPAIR
TABLE. The