Adds setting ForceListExpansion to provide a way to enable consistent handling of list parameters regardless of RDBMS
#1874
Conversation
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
…nt handling of list parameters regardless of RDBMS (DapperLib#1871)
|
Is there anything else I need to do for this pull request? The inconsistency of array handling is currently preventing me from being able to use arrays, so if there is more that needs to be done here, I'm willing to do so. |
|
Update: Resolved conflicts. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 implements a setting to allow opting-in to Dapper's list expansion even for databases that do not otherwise require it, in order to ensure consistent handling of lists for SQL designed to support multiple RDBMS.
Closes #1871.