Bug #70599 | visual explain displays the same plan for every query in a session | ||
---|---|---|---|
Submitted: | 10 Oct 2013 23:29 | Modified: | 12 Mar 2014 14:06 |
Reporter: | Joe Brown | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 6.0 | OS: | Windows (7.0) |
Assigned to: | CPU Architecture: | Any |
[10 Oct 2013 23:29]
Joe Brown
[11 Oct 2013 12:28]
MySQL Verification Team
Thank you for the bug report. I couldn't repeat using the mysql database 1sr query against user table 2nd query against db table. Please provide a complete test case with both queries. Thanks.
[11 Oct 2013 18:35]
Joe Brown
Here's the first query (both select from views): select c.descendant from v_causes_hierarchy c, v_causes_hierarchy h where c.distance = 3 and c.ancestor = h.ancestor and h.root = 1 and h.cause_version = c.cause_version and c.cause_version = 1 ; I run Visual Explain and get a nice looking graph. Then in another window I run the second query: select * from v_locations_hierarchy where version_id = 2 ; I run Visual Explain and get the exact same graph. Afterwards, no matter what I do, close and reopen tabs, try different queries, I always get the same Visual Explain graph.
[14 Oct 2013 15:04]
MySQL Verification Team
Please provide the create table/view (private if you wish). Thanks.
[15 Nov 2013 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[15 Nov 2013 1:08]
Joe Brown
create table foo (bar int); create view v_foo as select * from foo; that should do it.
[24 Jan 2014 16:15]
Alfredo Kojima
could you attach a screenshot?
[13 Mar 2014 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".