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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Parameter Usage on MultipleRowsCopy/MultipleRowsCopyAsync #2975
Allow Parameter Usage on MultipleRowsCopy/MultipleRowsCopyAsync #2975
Changes from all commits
16bd698
9caf4b9
cbec45a
74edd8c
ff4f35f
9b8e172
fab80eb
f391ad9
92ad512
7fab586
009331e
7d91b5f
2240547
12b1748
1a94108
848eea8
6b3a921
ed372fc
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Putting this as a virtual -feels- better, but I still ask whether we should let Max Length be tunable by the user or not (For Network round-trip purposes). I decided not, since
MaxBatchSize
is good enough to do the same most likely.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
COuld be usful. In baselines I see increase in number of roundtrips e.g. for DB2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it might be worth moving these, even with a simple Redirection for now, into a 'Bind' like method on
MultipleRowsHelper
. Over 15helper.
in a method feels like a smell to me.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need this check because there may be an edge case where even a single row was putting us over Max SQL limit.
Since we are now trying to be more correct here, we now 'back off' the last row when we go over
maxSqlLength
, rather than just continuing and hoping for the best. That said, we should still try to insert in case of Single row, and let provider fail if it really is an issue.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do this before finishFunction, in case
finishFunction
decides to add a parameter in future.