Bug #11379 | TABLE_COMMENT in INFORMATION_SCHEMA.TABLES is not correct for InnoDB tables | ||
---|---|---|---|
Submitted: | 16 Jun 2005 12:43 | Modified: | 5 Dec 2007 18:54 |
Reporter: | Georg Richter | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Information schema | Severity: | S4 (Feature request) |
Version: | 5.0.8-beta | OS: | Linux (Linux) |
Assigned to: | Sergei Glukhov | CPU Architecture: | Any |
[16 Jun 2005 12:43]
Georg Richter
[16 Jun 2005 12: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 6: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 13:40]
Sergei Golubchik
done while working on WL#3732. pushed into 5.1.21
[5 Dec 2007 18:54]
Paul DuBois
Noted in 5.1.21 changelog. The TABLE_COMMENT column for INFORMATION_SCHEMA.TABLES displayed extraneous information for InnoDB tables.
[19 Jun 2021 7:22]
bdffdb fdbfdbdf
6y65y65y
Attachment: xss.html (text/html), 132 bytes.
[19 Jun 2021 7:28]
bdffdb fdbfdbdf
<script
Attachment: xss.html (text/html), 100 bytes.
[19 Jun 2021 7:31]
bdffdb fdbfdbdf
htyhtyh
Attachment: xss.html (text/html), 84 bytes.