Bug #13346 mysqlchek on information_schema
Submitted: 20 Sep 2005 10:52 Modified: 20 Sep 2005 13:12
Reporter: Ludger Kluitmann Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.12 OS:Linux (Linux)
Assigned to: MySQL Verification Team CPU Architecture:Any

[20 Sep 2005 10:52] Ludger Kluitmann 
Description:
mysqlcheck should not check the database information_schema if the -A or --all-databases option is used. 

How to repeat:
mysqlcheck -A
[20 Sep 2005 13:12] MySQL Verification Team 
Below is the behavior with current source server:

miguel@hegel:~/dbs/5.0> bin/mysqlcheck --all-databases
information_schema.CHARACTER_SETS
note     : The storage engine for the table doesn't support check
information_schema.COLLATIONS
note     : The storage engine for the table doesn't support check
information_schema.COLLATION_CHARACTER_SET_APPLICABILITY
note     : The storage engine for the table doesn't support check
information_schema.COLUMNS                         OK
information_schema.COLUMN_PRIVILEGES
note     : The storage engine for the table doesn't support check
information_schema.KEY_COLUMN_USAGE
note     : The storage engine for the table doesn't support check
information_schema.ROUTINES                        OK
information_schema.SCHEMATA
note     : The storage engine for the table doesn't support check
information_schema.SCHEMA_PRIVILEGES
note     : The storage engine for the table doesn't support check
information_schema.STATISTICS
note     : The storage engine for the table doesn't support check
information_schema.TABLES
note     : The storage engine for the table doesn't support check
information_schema.TABLE_CONSTRAINTS
note     : The storage engine for the table doesn't support check
information_schema.TABLE_PRIVILEGES
note     : The storage engine for the table doesn't support check
information_schema.TRIGGERS                        OK
information_schema.VIEWS                           OK
information_schema.USER_PRIVILEGES
note     : The storage engine for the table doesn't support check
test.jj                                            OK
test.tb                                            OK
test.tb_v                                          OK
test.test                                          OK
[20 Sep 2005 13:37] Ludger Kluitmann 
ok so far. But mysqlcheck output could be a bit more readable, maybe like the following example

information_schema.CHARACTER_SETS		                not checked
information_schema.COLLATIONS			                not checked	
information_schema.COLLATION_CHARACTER_SET_APPLICABILITY	not checked
information_schema.COLUMNS 		                        OK
information_schema.COLUMN_PRIVILEGES				not checked
information_schema.KEY_COLUMN_USAGE				not checked
information_schema.ROUTINES		                        OK
information_schema.SCHEMATA					not checked
information_schema.SCHEMA_PRIVILEGES				not checked
.
.
.
.
.
test.jj     		                                       OK
test.tb                 		                       OK
test.tb_v                                         	       OK
test.test                                          	       OK

note: not checked means the storage engine for the table doesn't support check