Update affected_rows after calling mysql_next_result#1412
Merged
sodabrew merged 1 commit intobrianmario:masterfrom Oct 3, 2025
Merged
Update affected_rows after calling mysql_next_result#1412sodabrew merged 1 commit intobrianmario:masterfrom
affected_rows after calling mysql_next_result#1412sodabrew merged 1 commit intobrianmario:masterfrom
Conversation
Fix: brianmario#1411 Followup: brianmario#1383 When using multi statement, we need to update the affected rows after each call to `mysql_next_result`.
Collaborator
|
lgtm! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix: #1411
Followup: #1383
When using multi statement, we need to update the affected rows after each call to
mysql_next_result.