Bug #62454 Workbench repeats the last warning in the following commands after the one that
Submitted: 16 Sep 2011 21:21 Modified: 18 Jul 2012 19:15
Reporter: denixx baykin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.34 CE Revision 7780 OS:Windows (Win XP SP3)
Assigned to: CPU Architecture:Any
Tags: warnings, workbench

[16 Sep 2011 21:21] denixx baykin 
Description:
Workbench repeats the last warning in the following commands after the one that has a warning.
Repeat code below and commands executed after DROP will show warnings.

How to repeat:
CREATE SCHEMA `test` DEFAULT CHARACTER SET utf8 ;

CREATE  TABLE `test`.`testutf8mb4` (
  `testValue` VARCHAR(50) NOT NULL ,
  PRIMARY KEY (`testValue`) );

USE `test`;
DROP procedure IF EXISTS `testRecord`;
DELIMITER $$
USE `test`$$
CREATE PROCEDURE `testRecord`(
    _testValue VARCHAR(50)
)
BEGIN
IF EXISTS (select 1 from `test`.`testutf8mb4` where testValue = _testValue)
THEN 
select CONCAT('testValue: ', _testValue, ' already exists.');
ELSE INSERT INTO `test`.`testutf8mb4` (
        `testValue`
    ) VALUES (
        _testValue
    );
select CONCAT('testValue: ', _testValue, ' Record added.');
END IF;
END
$$
DELIMITER ;
[17 Sep 2011 12:37] denixx baykin 
Setting to S3 because It's not a feature request.
[17 Sep 2011 12:38] denixx baykin 
Version refinement.
[28 Mar 2012 18:05] Alfredo Kojima 
bug #64781 is a duplicate
[4 Jul 2012 15:03] Marcin Szalowicz 
the same thing is on Ubuntu 12.04/amd64 with wb 5.2.40

steps to reproduce:
issue statement that produce warning
issue statement: USE $dbname
[18 Jul 2012 19:15] Philip Olson 
This has been fixed as of the soon-to-be-released Workbench 5.2.41, and 
here's the changelog entry:

MySQL Workbench would sometimes repeat a warning during a successful action
that followed the action with the warning.