Fix #2028 #2133
Open
Fix #2028 #2133
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
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.
This fixes issue #2028 that occurs when executing
ExecuteAsyncon aCommandDefinitionwithPipelinedcommand flag in combination with multiple parameters on theMicrosoft.Data.SqlClientand withMultipleActiveRecordSetsset totrue.I simply applied the fix proposed in the issue and added a test to ensure that the issue is not occuring.
As far as I understand, the original version runs
ExecuteNonQueryAsyncon aDbCommandbut disposes this command before awaiting the resultExecuteNonQueryAsync. With this fix this behavior is turned around. However, I am not sure how this affects other drivers, or why this issue did not occur with theSystem.Data.SqlClientdriver.