Bug #73452 | Vertical Output doesn't support multiple resultsets | ||
---|---|---|---|
Submitted: | 1 Aug 2014 10:33 | Modified: | 28 Aug 2014 22:01 |
Reporter: | Daniël van Eeden (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 6.1.7 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | Output, PROCEDURE, ResultSet, vertical |
[1 Aug 2014 10:33]
Daniël van Eeden
[1 Aug 2014 11:40]
MySQL Verification Team
Hello Daniël, Thank you for the report. Verified as described. Thanks, Umesh
[1 Aug 2014 11:44]
MySQL Verification Team
## Create sample proc use test; delimiter // DROP PROCEDURE IF EXISTS simpleproc// CREATE PROCEDURE simpleproc() BEGIN SELECT user(); SELECT database(); END// delimiter ; Run "CALL simpleproc; with "Query" > "Execute Current Statment (Vertical Text Output)" > call simpleproc ******************** 1. row ********************* user(): ******************************** 1 rows in set ## MySQL> prompt mysql> delimiter // mysql> DROP PROCEDURE IF EXISTS simpleproc// Query OK, 0 rows affected, 1 warning (0.00 sec) mysql> CREATE PROCEDURE simpleproc() -> BEGIN -> SELECT user(); -> SELECT database(); -> END// Query OK, 0 rows affected (0.00 sec) mysql> mysql> delimiter ; mysql> mysql> call simpleproc\G *************************** 1. row *************************** user(): root@localhost 1 row in set (0.00 sec) *************************** 1. row *************************** database(): test 1 row in set (0.00 sec) Query OK, 0 rows affected (0.00 sec)
[28 Aug 2014 22:01]
Philip Olson
Fixed as of the upcoming MySQL Workbench 6.2.2 release, and here's the changelog entry: When there were multiple result sets, then only one was shown in the output pane when using "Vertical Output" output type. Thank you for the bug report.