Skip to content

fix: display result sets from stored procedure calls (CALL/EXEC/EXECUTE) - #265

Closed
probeldev wants to merge 1 commit into
Maxteabag:mainfrom
probeldev:fix-display-stored-procedure-results
Closed

fix: display result sets from stored procedure calls (CALL/EXEC/EXECUTE)#265
probeldev wants to merge 1 commit into
Maxteabag:mainfrom
probeldev:fix-display-stored-procedure-results

Conversation

@probeldev

Copy link
Copy Markdown
Contributor

Currently, queries like CALL getalltheme() are classified as non-queries, so the UI only shows 61 row(s) affected instead of the actual result set. This PR treats stored procedure calls as row-returning queries and adds MySQL-specific handling for multiple result sets.

Before:
Screenshot 2026-07-07 at 11 13 02

After:
Screenshot 2026-07-07 at 11 13 44

Copy link
Copy Markdown
Owner

Thank you @probeldev for the original implementation. I confirmed the result-set bug and carried the fix forward in #287, with provider-specific routing plus regression coverage for MySQL/MariaDB and SQL Server. That replacement also preserves Oracle/Firebird non-query behavior, drains all result sets, and distinguishes SQL Server stored procedures from EXECUTE AS and dynamic SQL. #287 is now merged, so I’m closing this PR as superseded.

@Maxteabag Maxteabag closed this Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants