Bug #59221 | "show warnings" statement does not appear to be working - returns 0 records | ||
---|---|---|---|
Submitted: | 29 Dec 2010 20:33 | Modified: | 1 Sep 2011 16:25 |
Reporter: | Samir Abboushi | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S1 (Critical) |
Version: | 5.2.30 CE Rev. 6790, 5.2.31 | OS: | Any (Windows Vista 64, Mac OS X) |
Assigned to: | CPU Architecture: | Any | |
Tags: | show warnings |
[29 Dec 2010 20:33]
Samir Abboushi
[30 Dec 2010 18:32]
Valeriy Kravchuk
Thank you for the bug report. Verified with simple test case like this: mysql> set sql_mode=''; Query OK, 0 rows affected (0.00 sec) mysql> create table tt(c1 int); Query OK, 0 rows affected (0.07 sec) mysql> insert into tt values('abc'); Query OK, 1 row affected, 1 warning (0.01 sec) mysql> show warnings\G *************************** 1. row *************************** Level: Warning Code: 1366 Message: Incorrect integer value: 'abc' for column 'c1' at row 1 1 row in set (0.00 sec) As you can see, we have a warning in this case in mysql command line client. Same actions in Workbench does not give any information about warnings in the Output tab, and SHOW WARNINGS returns nothing...
[24 Apr 2011 18:02]
Alfredo Kojima
bug #60967 is a duplicate
[27 Apr 2011 11:55]
Valeriy Kravchuk
Bug #60967 was marked as a duplicate of this one.
[1 Sep 2011 16:25]
Philip Olson
Fixed as of 5.2.34: + A <literal>SHOW WARNINGS</literal> query would return zero + results, even when warnings existed.