Bug #69283 not quoting database, table, index names with backticks....
Submitted: 20 May 2013 3:04 Modified: 11 Jul 2013 22:37
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Utilities Severity:S3 (Non-critical)
Version:1.3.1 OS:Windows
Assigned to: CPU Architecture:Any

[20 May 2013 3:04] Shane Bester
Description:
please quote every single identifier with backticks to avoid syntax errors when running the generated sql.  e.g.

H:\util>mysqlindexcheck --server=root@127.0.0.1 test  --show-drops
# Source on 127.0.0.1: ... connected.
# The following indexes are duplicates or redundant for table test.t:
#
CREATE INDEX create_2 ON test.t (create) USING BTREE
#     may be redundant or duplicate of:
CREATE INDEX create ON test.t (create, b) USING BTREE
#
# DROP statements:
#
ALTER TABLE test.t DROP INDEX create_2;
#

How to repeat:
create table t(`create` int, b int,key(`create`,b),key(`create`));
mysqlindexcheck --server=root@127.0.0.1 test

Suggested fix:
quote identifiers with backticks
[11 Jul 2013 22:37] Philip Olson
Fixed as of MySQL Utilities 1.2.4/1.3.3, and here's the changelog entry:

The "mysqlindexcheck" utility was not quoting objects identifiers with
backticks in the generated SQL.

Thank you for the bug report.