[Bug]: MySQL stored procedures returning multiple result sets only display the first result set

[arnabmunshi-shbl]

Describe the bug

Describe the bug
When executing a stored procedure that returns multiple result sets, tabularis only displays the first result set. The remaining result sets are not shown.

The same stored procedure returns all result sets correctly when executed in MySQL Workbench.

Screenshots
Providing screenshots for comparing the output from tabularis and MySQL Workbench.
MySQL Workbench
tabularis

Application:

• App client: MySQL
• App version: 0.13.4
• Installation source: tabularis_0.13.4_x64_en-US.msi

Environment:

• OS name: Windows 11 Pro
• OS version: 25H2
• DB name: MySQL
• DB version: 8.0.46-0ubuntu0.24.04.3

To Reproduce

1. Connect to a MySQL database using tabularis.
2. Execute a stored procedure that returns multiple result sets (multiple SELECT statements).
3. Observe that only the first result set is displayed.
4. Execute the same stored procedure in MySQL Workbench.
5. Observe that all result sets are returned correctly.

OS Version

Windows 11 Pro, 25H2

Tabularis Version

0.13.4

Relevant Log Output

The stored procedure intentionally returns multiple result sets using multiple SELECT statements.

Example:


CREATE PROCEDURE sp_test()
BEGIN
    SELECT 'First result' AS message;
    SELECT 'Second result' AS message;
    SELECT 'Third result' AS message;
END;


Expected output:

Result Set 1: `First result`
Result Set 2: `Second result`
Result Set 3: `Third result`

Actual behavior in tabularis:

- Only Result Set 1 is displayed.

Actual behavior in MySQL Workbench:

- All three result sets are displayed correctly.

I'm not sure whether this is a missing feature or a bug, but it prevents working with stored procedures that intentionally return multiple result sets.

[debba]

Hi @arnabmunshi-shbl ,
thanks for feedback.
Would you like to create a PR for it?

[debba]

Hi @arnabmunshi-shbl,

this should be fixed by #415: statements returning multiple result sets (like your CALL sp_test()) now render each result set in its own result tab, the same way MySQL Workbench shows them.

Could you test it once a build of that branch is available and confirm it works with your real procedures?

One note on the snippet in the issue: it's missing the DELIMITER directives, so as written it won't create the procedure in most SQL clients (the client splits on the ; inside the body). Make sure to create it like this:

DELIMITER //
CREATE PROCEDURE sp_test()
BEGIN
    SELECT 'First result' AS message;
    SELECT 'Second result' AS message;
    SELECT 'Third result' AS message;
END//
DELIMITER ;

That part is standard MySQL client behaviour (Workbench does the same, it just handles DELIMITER in its own statement splitter — as Tabularis does) and is unrelated to the bug itself, which was purely about displaying the additional result sets.