#4054 (ok 4.0.6) query analysis doesn't launch in status monitor

4.0.5
fixed
None
1
2013-09-05
2013-08-13
No

when selecting Query analyser in Status monitor, it doesn't load.
"In Status > Monitor, you can select a portion of the graph and a panel
shows a time range. Then you can display the corresponding queries, and
these are clickable. You should be able to obtain an analysis of this
query but nothing happens."

Discussion

1 2 > >> (Page 1 of 2)
  • PMA_SQLPrettyPrint seems to be distorting the query in monitor's analyzer, skipped it's use there for now.

     
    • summary: query analysis doesn't launch in status monitor --> (ok 4.0.6) query analysis doesn't launch in status monitor
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,2 +1,5 @@
     when selecting Query analyser in Status monitor, it doesn't load.
    -Ask lem9 or roccivic.
    +"In Status > Monitor, you can select a portion of the graph and a panel
    +shows a time range. Then you can display the corresponding queries, and
    +these are clickable. You should be able to obtain an analysis of this
    +query but nothing happens."
    
    • status: open --> resolved
    • assigned_to: Atul Pratap Singh
    • Priority: 5 --> 1
     
  • Marc Delisle
    Marc Delisle
    2013-08-17

    Atul,
    I still have the problem in Firefox (Iceweasel 17.0.8 on Debian). I briefly see "Analysing..." but that's all.

     
  • Marc,
    I don't have Icewease, but I can see it working on Firefox 16.0.1(Ubuntu). I fixed it in QA_4_0, didn't port to master yet.

     
  • Marc Delisle
    Marc Delisle
    2013-08-17

    Atul,
    I did some tracing with Firebug. The problem happens everytime for me. The error I get in server_status_monitor is that data.explain does not exist.

     
  • data.explain undefined was the actual problem that I saw too, and it was because of distorted SQL query being sent. Do you still notice the distorted query in the analyzer dialog's codemirror area? If yes, then please ensure:

    1) that the browser cache is cleared.
    2) that we are checking the same branch QA_4_0.

    If you already did that and it didn't work, we got to see if others experience the same problem too, anyway it works fine in my Firefox/Chrome.

     
  • Marc Delisle
    Marc Delisle
    2013-08-18

    Atul,
    I am testing with QA_4_0 at commit 3df8d3db6ba10c3ad7675727a750f2ba74a41d51. I have cleared the browser cache. The query I see in the codemirror area is "SELECT * FROM employees ORDER BY employees.last_name ASC
    LIMIT 0, 30" on two lines.

     
  • Marc Delisle
    Marc Delisle
    2013-08-18

    Atul,
    what happens in server_status_monitor.php is that, at the point of running the EXPLAIN query, we are not positionned at the correct db. Tracing after the PMA_DBI_try_query() gives me
    '#1146 - Table 'mysql.employees' doesn't exist
    but it should be trying this on employees.employees.

     
  • Yes, turns out it depends on type of query. I checked in QA_3_5 too, there the analyzer explicitly gives the error message "#1046 - No database selected"

     
    • summary: (ok 4.0.6) query analysis doesn't launch in status monitor --> query analysis doesn't launch in status monitor
    • status: resolved --> open
     
1 2 > >> (Page 1 of 2)