MySQL Bugs: #24049: WARNINGS not displayed

Bug #24049	WARNINGS not displayed
Submitted:	7 Nov 2006 16:30	Modified:	8 Jan 2007 15:02
Reporter:	Yahoo Serious (Silver Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.2.4 beta/1.2.5	OS:	Windows (Windows 2000)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
QB does not show the warnings caused by a query.  Even if MySQL-example predicts a warning (http://dev.mysql.com/doc/refman/5.0/en/show-warnings.html).
Issuing a SHOW WARNINGS immediately after a command does not show anything, because the session is closed.

Related to Bug #24048 and possibly to Bug #22576.

How to repeat:
Issue a command that would trigger a warning.
MySQL manual suggests:
  http://dev.mysql.com/doc/refman/5.0/en/show-warnings.html
  CREATE TABLE t1 (a TINYINT NOT NULL, b CHAR(4)) TYPE=MyISAM;
and watch nothing appear...

Suggested fix:
Possible fixes:
 - show warnings in error-description-window, (or in a new warning-description-window),
 - add possibility to keep session open after query/command

Thank you for the bug report. I think this would be a feature request

Maybe this theoretically is not a bug, but it is a big shortcoming.  It is missing functionality without workaround, which seems pretty essential. 

The policy states S3 as "involves a partial or limited loss of non-critical functionality", whereas S4 has "no impact on the quality, performance, or functionality of the product in a production system."  

I think this is missing functionality, although maybe not a literal "loss", if QB never supported it(?).  As Domas Mituzas implies in Bug #23787, this may be considered a bug: "A request for obviously missing functionality. Verified, as there's no easy workaround [...]".

[BTW: the definitions-link on Severity is broken, it should refer not refer to policies-17.html but to http://www.mysql.com/company/legal/supportpolicies/policies-11.html]

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