Batch.execute() Serializes Statement Execution #15
Conversation
This file contains 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
Fix typo Co-authored-by: Jean de Lavarene <jean.de.lavarene@oracle.com>
Fix typo Co-authored-by: Jean de Lavarene <jean.de.lavarene@oracle.com>
Douglas-Surber
approved these changes
Apr 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 for Issue #5
It is now required to fully-consume each Result emitted by Oracle R2DBC's Batch.execute() Publisher. The Publisher does not emit the next Result until the update count or row data of a previous Result has been consumed.
This ensures that a Statement will never be executed while the row data of a Result is being consumed concurrently. Concurrent database operations lead to blocked threads, which may lead to a deadlock, as described in Issue #5.