Bug #54390 | Allow a special "trace" comment usage in MEM's query analyzer | ||
---|---|---|---|
Submitted: | 10 Jun 2010 8:10 | ||
Reporter: | Jonathon Coombes | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Enterprise Monitor | Severity: | S4 (Feature request) |
Version: | 2.2.0.1696 | OS: | Any |
Assigned to: | Mark Leith | CPU Architecture: | Any |
Tags: | mem, Merlin, quan, query analyzer |
[10 Jun 2010 8:10]
Jonathon Coombes
[24 Jun 2010 14:57]
Enterprise Tools JIRA Robot
Mark Leith writes: Verified - we actually were not passing back any comments from the proxy, even for the example query, where we do maintain comments, and have section in the popup for them. We should just strip the first comment token for this new section, stripping all comments and filling in that section may not make sense for context sensitive comments within queries. Optionally provide some way of describing where the query came from in our part of the stack, as well from Proxy. For instance Connector/J uses the comment section to report: "Reported by MySQL Enterprise Plugin for Connector/J ..."
[24 Jun 2010 15:23]
Enterprise Tools JIRA Robot
Mark Leith writes: Note however, comments are *not* stripped for example queries - so you should already still see the comments in the full example query text.