Bug #41576 REPAIR TABLE: Manual section is too MyISAM-centric

• Submitted: 18 Dec 2008 2:59
• Modified: 18 Dec 2008 9:11
• Reporter: Paul DuBois
• Status: Verified
• Category: MySQL Server: General
• Severity: S4 (Feature request)
• Version: all
• OS: Any
• CPU Architecture: Any

[18 Dec 2008 2:59] Paul DuBois

Description:
The REPAIR TABLE section of the manual is in need of improvement.

Initially REPAIR TABLE worked for MyISAM tables. As a result, the
manual section is very MyISAM-centric. Now REPAIR TABLE can be used
for other storage engines (ARCHIVE, CSV), so the heavy MyISAM
emphasis makes the section confusing in several ways:

* It's said that by default, REPAIR TABLE is like myisamchk --recover.
That makes sense for MyISAM, but what does it mean for other storage
engines?

* The QUICK and EXTENDED options are described in comparison to
myisamchk. Example:

If QUICK is given, REPAIR TABLE tries to repair only the index tree.
This type of repair is like that done by myisamchk --recover --quick.

Do these options have any meaning for other storage engines?

* The USE_FRM option is described in terms of .MYI files. What does
this option mean in relation to other storage engines?

So, some questions:

* For the statements that compare REPAIR TABLE operations with
myisamchk operations, how do these apply, if at all, to other storage
engines?

* How do the QUICK, EXTENDED, and USE_FRM options apply to non-MyISAM
storage engines? Are they ignored?

How to repeat:
By inspection of http://dev.mysql.com/doc/refman/5.1/en/repair-table.html