Bug #11379 TABLE_COMMENT in INFORMATION_SCHEMA.TABLES is not correct for InnoDB tables
Submitted: 16 Jun 2005 14:43 Modified: 5 Dec 2007 19:54
Reporter: Georg Richter
Status: Closed
Category:Server: I_S Severity:S4 (Feature request)
Version:5.0.8-beta OS:Linux (Linux)
Assigned to: Sergey Gluhov Target Version:
Triage: D5 (Feature request)

[16 Jun 2005 14:43] Georg Richter 
Description:
The table_comment column in INFORMATION_SCHEMA.TABLES doesn't contain correct information
( "InnoDB free" ... will be always concatenated to the comment)

How to repeat:
create table test.x1 (a int) engine=myisam comment='this is the first table';
create table test.x2 (a int) engine=innodb comment='this is the second table';

select table_name, table_comment from information_schema.tables where table_schema='test'
and table_name like 'x_' \G

Output:
*************************** 1. row ***************************
   table_name: x1
table_comment: this is the first table
*************************** 2. row ***************************
   table_name: x2
table_comment: this is the second table; InnoDB free: 658432 kB
2 rows in set (0.20 sec)
[16 Jun 2005 14:49] Marko Mäkelä 
The comment is appended to in ha_innobase::update_table_comment(). There should be another
interface for returning that information.
[18 Jun 2005 8:38] Vasily Kishkin 
Tested on Win 2000 Sp4, MySQL server 5.0.8 beta

mysql> select table_name, table_comment from information_schema.tables where
    -> table_schema='test' and table_name like 'x_' \G
*************************** 1. row ***************************
   table_name: x1
table_comment: this is the first table
*************************** 2. row ***************************
   table_name: x2
table_comment: this is the second table; InnoDB free: 11264 kB
2 rows in set (0.14 sec)
[5 Dec 2007 14:40] Sergei Golubchik 
done while working on WL#3732.
pushed into 5.1.21
[5 Dec 2007 19:54] Paul DuBois 
Noted in 5.1.21 changelog.

The TABLE_COMMENT column for INFORMATION_SCHEMA.TABLES displayed
extraneous information for InnoDB tables.