Bug #55 SHOW WARNINGS returns empty resultset
Submitted: 4 Feb 2003 0:01 Modified: 11 Nov 2004 12:01
Reporter: Georg Richter Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1 OS:Linux (Linux 2.4)
Assigned to: CPU Architecture:Any

[4 Feb 2003 0:01] Georg Richter
Description:
SHOW WARNINGS doesn't return any warnings for a SELECT Statement

If this is an expected behaviour, it should be documented.

How to repeat:
mysql> create table a (a int); 
Query OK, 0 rows affected (0.00 sec) 

mysql> insert into a values (1),(NULL); 
Query OK, 2 rows affected (0.00 sec) Records: 2 Duplicates: 0 Warnings: 0 

mysql> create table b (a int not null); 
Query OK, 0 rows affected (0.00 sec) 

mysql> insert into b select * from a; Query OK, 2 rows affected (0.00 sec) Records: 2 Duplicates: 0 Warnings: 1 

mysql> show warnings; Empty set (0.00 sec)
[25 Mar 2003 2:51] Michael Widenius
Sorry, but the bug system is not the appropriate forum for asking
support questions. Your problem is not the result of a bug.
For a list of more appropriate places to ask for help using MySQL
products, please visit http://www.mysql.com/support/

Thank you for your interest in MySQL.

Warnings is a new feature in 4.1.

We are adding warnings for things that can be critical first (like not existing tables in DROP TABLE IF EXIST) before starting to add warnings for auto conversions like in the INSERT case.

In other words, this is a not implemented feature that will come in future releases.
[11 Nov 2004 12:01] Georg Richter
Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 
http://www.mysql.com/downloads/

Additional info: