Skip to content

Conversation

@enebo
Copy link
Member

@enebo enebo commented Jun 6, 2025

Try and reduce how much result set processing or ruby results are made

@seuros
Copy link
Contributor

seuros commented Jun 6, 2025

Correct me if I'm wrong, but you used an early exit strategy ?

It should work.

@enebo
Copy link
Member Author

enebo commented Jun 6, 2025

@seuros I think what I am trying may not work because getMoreResults may invalid the previous unprocessed resultset. I am going to only do the removal of empty resultset change.

@enebo enebo closed this Jun 6, 2025
@enebo enebo deleted the last_result branch June 6, 2025 18:45
@enebo
Copy link
Member Author

enebo commented Jun 6, 2025

@seuros sorry I did not answer your question either. I added another commit but it was changed to return there only if there was no next statement or no count so it would not exit early. First version would not exit early for sequence of resultsets but would have if it was a query followed by non-resultset statement. So it was partially broken. Also JDBC doesn't allow it making the PR moot.

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.

3 participants