MySQL Bugs: #12782: MQB can't properly handle CALL of a procedure that returns multiple resultsets

Bug #12782	MQB can't properly handle CALL of a procedure that returns multiple resultsets
Submitted:	24 Aug 2005 11:37	Modified:	28 Sep 2005 10:36
Reporter:	Anders Karlsson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.13	OS:	Windows (Windows)
Assigned to:		CPU Architecture:	Any

Description:
When running a procedure through a CALL in a results set tab window, then the result text of the CALL statement is cleared from the edit window. The correct # of resultset windows are shown the first time. If run again, by typing in the same CALL statement again, only one of the result windows is reused, the other one persists, which makes for a strange look of things.

How to repeat:
- Connect to MySQL test database from MQB
- Rightclick in the schemata window and select "Create New Procedure/Function"
- Name the procedure p1 and click the "Create PROCEDURE" button.
- Edit the procedure to look like this:
DELIMITER $$

DROP PROCEDURE IF EXISTS `hrf2`.`p1`$$
CREATE PROCEDURE `hrf2`.`p1` ()
BEGIN
  SELECT 1;
  SELECT 2;
END$$

DELIMITER ;

- Rightclick in the script window and select "Add New Resulset Tab".
- In the editor window at the top, type:
CALL p1()

- Click the "Execute" button.
- The "CALL p1()" text is removed, two resultsets are shown.
- Type "CALL p1()" in the editor window again.
- Click the "Execute" button again.
- The "CALL p1()" text is removed and there are three resulsets shown.

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/