Bug #45431 | "select * from 23lk4kj234;" is reported incorrectly in query analyzer | ||
---|---|---|---|
Submitted: | 10 Jun 2009 14:28 | Modified: | 21 Jul 2009 12:17 |
Reporter: | Josh Sled | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Agent | Severity: | S3 (Non-critical) |
Version: | 2.1.0.1059 | OS: | Any |
Assigned to: | Kay Roepke | CPU Architecture: | Any |
Tags: | quan, tokenizer |
[10 Jun 2009 14:28]
Josh Sled
[10 Jun 2009 14:36]
Kay Roepke
The table name is valid, but the canonical form is wrong. I suspect that the proxy's tokenizer is breaking this, because: mysql> select * from 23l4kj234; ERROR 1146 (42S02): Table 'test.23l4kj234' doesn't exist mysql> create table 23l4kj234 (a int); Query OK, 0 rows affected (0.05 sec) mysql> select * from 23l4kj234; Empty set (0.00 sec) is what I would expect. Bumping up
[10 Jun 2009 15:02]
Diego Medina
Verified as described on 2.1.0.1059 On the agent log I see: <datum> <target> <namespace>mysql</namespace> <classname>statementsummary</classname> <instance>c7e5bf20-c266-4c7b-8e1c-451f93b28ee6.quan_test.749822bd7e442d18eddedfd8c3e46523</instance> <attribute>text</attribute> </target> <utc>2009-06-10T14:59:11.385Z</utc> <value>SELECT * FROM ? l4kj234 </value> </datum> and later I see <datum> <target> <namespace>mysql</namespace> <classname>statement</classname> <instance>c7e5bf20-c266-4c7b-8e1c-451f93b28ee6.quan_test.749822bd7e442d18eddedfd8c3e46523.1</instance> <attribute>text</attribute> </target> <utc>2009-06-10T14:59:13.961Z</utc> <value>select * from 23l4kj234</value> </datum>
[13 Jul 2009 13:46]
Enterprise Tools JIRA Robot
Keith Russell writes: Patch installed in versions => 2.1.0.1076.
[14 Jul 2009 19:54]
Enterprise Tools JIRA Robot
Diego Medina writes: Verified fixed on 2.1.0.1076
[21 Jul 2009 12:17]
Tony Bedford
An entry was added to the 2.1.0 changelog: The query SELECT * FROM 23lk4kj234; was reported incorrectly in the Query Analyzer.