MySQL Bugs: #47: MySQLcheck does not correctly recognises "Table handler does not support check"

Bug #47	MySQLcheck does not correctly recognises "Table handler does not support check"
Submitted:	28 Jan 2003 14:31	Modified:	27 Sep 2008 8:13
Reporter:	Peter Zaitsev (Basic Quality Contributor)	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S3 (Non-critical)
Version:	4.1	OS:	Any (all)
Assigned to:	Jani Tolonen	CPU Architecture:	Any

Description:
If you check HEAP/ISAM etc table and it is also attempted to be 
repaired while it does not need to.... this is not critical one 
of course:

StateRecords.itinerary_state_records_20030124_2200 Table is 
already up to date
StateRecords.newstaterecords
error    : The handler for the table doesn't support check/repair
StateRecords.staterecords_20021202                 Table is 
already up to date
mysql.tables_priv                                  Table is 
already up to date
mysql.user                                         Table is 
already up to date

Repairing tables
StateRecords.newstaterecords
error    : The handler for the table doesn't support check/repair

How to repeat:

create table a(i int) type=heap;

On the console

mysqlcheck -c --auto-repair test

MySQLcheck will attemp to repair this table while it should not.
This can be confusing for unexperienced users.

This is relevant for 3.23 and 4.0 but we will not fix this until 4.1

Suggested fix:

Add in 4.1 a new column Msg_id that will contain the message id for the error.  When we have this we can
skip not relevant errors in mysqlcheck

Trying with 5.0 version of mysqlcheck:
mysql> create table a(i int) engine=heap;
Query OK, 0 rows affected (0.01 sec)
kostja@bodhi:~$ mysqlcheck -c --auto-repair test
test.a
note     : The storage engine for the table doesn't support check
test.t1                                            OK
test.t2                                            OK
kostja@bodhi:~$ 

I assume this bug was fixed.