Bug #28688 Explain results populated into incomplete resultset pane
Submitted: 25 May 2007 19:27 Modified: 4 Jun 2009 12:58
Reporter: Clifton Kilby III Email Updates:
Status: Won't fix Impact on me:
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.2.10/1.2.12 OS:Windows (XP Pro SP2)
Assigned to: CPU Architecture:Any

[25 May 2007 19:27] Clifton Kilby III
When viewing the Explain results, the explain resultset is populated into an incomplete/special resultset pane. It is possible to promote this to a resultset tab. The product of this action is missing the edit resultSet toolbar and status bar at the bottom of the screen.

How to repeat:
In QB, create a simple SELECT statment. You should have one resultset pane open.
Click the explain button.
You should now have the results in the top pane, and the explain in the middle pane. There is a small error dialogue at the bottom with extended information.
Right click in the upper resultset pane, remove resultset.
This promotes the middle pane to the top. You now have an incomplete resultset pane.
Future use of this pane for SELECT queries functions normally until you attempt to edit a result set. As its missing the toolbar, this isn't possible (without hotkeys). Also, should you attempt to use the Explain button on this resultset pane, it will automatically discard the results, and repopulate with the explain extended query. 
The actual action is that the query is overwritten with the EXPLAIN EXTENDED generated query. Further clicking of the Explain button will continue prefixing the query with EXPLAIN EXTENDED repeatedly.

Suggested fix:
A resultset that was used for Explain extended should be checked for this promotion and given the status/edit toolbar. Also the resultset's internal pointer to its EXPLAIN EXTENDED resultset pane should be removed when this promotion happens so that future Explains on that resultset are populated into a new EXPLAIN EXTENDED resultset pane.
[26 May 2007 0:47] MySQL Verification Team
Thank you for the bug report.
[4 Jun 2009 12:58] Axel Schwenke
Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Query Browser into MySQL Workbench. We won't fix uncritical bugs in Query Browser anymore.

More information on MySQL Workbench: