MySQL Bugs: #22576: EXPLAIN EXTENDED (query) does not produce the extended result

Bug #22576	EXPLAIN EXTENDED (query) does not produce the extended result
Submitted:	22 Sep 2006 0:33	Modified:	8 Jan 2007 12:36
Reporter:	Clifton Kilby III	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.2.3 beta	OS:	Windows (XP Pro SP 2)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
Running EXPLAIN EXTENDED on a SELECT query showed an error dialog with the optimizer's query in version 1.1.9. I upgraded to MySQL Tools for 5.0 and am now using 1.2.3 beta. EXPLAIN EXTENDED now only produces the EXPLAIN result without the error box that has the optimizer query in it.
Using MySQL 5.0.18-nt via TCP/IP for both 1.1.9 (working) and 1.2.3 beta (non-working)
Issuing a SHOW WARNINGS immediately after the EXPLAIN EXTENDED did not show the EXTENDED information either (no data returned).

How to repeat:
Run EXPLAIN EXTENDED on any valid SELECT query.

Suggested fix:
Ensure that the optimizer result is loaded into the error box, or that it is shown in its own window.

Thank you for a problem report. Verified just as described. There should be some way to get EXPLAIN EXTEMDED resuls in QB.

My guess would be that this optimized query is not an error, so it is not displayed: see Bug #24049.

My question would be:
 a)  did QB change the message types displayed?
 b)  or did MySQL (server) change the message type of the result (the optimized query)?
(message types being error, warning, or something else)?

If you did not (also) change the MySQL-version, it would suggest a) .
Just my two cents.

The two bug reports look to be different issues to me.

I am using the same MySQL server for both trials, the 1.1.x would display the optimizer output as an error. This is expected behavor, explain extended outputs the optimizer query in the error message.

1.2.3 has an error field and for me outputs expected syntactial and logical errors, which would indicate it is still handling the error checking. It just appears that for whatever reason, QB is not displaying error information for EXPLAIN EXTENDED

Well , it is not displaying immediately, because it is qualified as a "warning", as explained in the manual:

http://dev.mysql.com/doc/refman/5.0/en/explain.html
---
When the EXTENDED keyword is used, EXPLAIN produces extra information that can be viewed by issuing a SHOW WARNINGS statement following the EXPLAIN statement.
---

So it is not displayed immediately as described in Bug #24049.  However, that 'bug' is considered a <feature request>, whereas this one is considered a <bug>...

SHOW WARNINGS does not display it because you have a new session.  I think this needs to be changed, as described in feature request: Bug #24048.

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html