Workaround Bulk Copy for batch insert operation against specific datatypes. #908
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
…ure-DW-Junit # Conflicts: # src/test/java/com/microsoft/sqlserver/jdbc/bvt/BvtTest.java
|
PR moved to #912. |
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.
For now, these datatypes don't seem to work against Azure DW when using bulk copy:
Money/Smallmoney
Temporal data types (Date, Datetime, Datetime2, SmallDateTime, DateTimeOffset, Time).
This PR puts a workaround that makes tables with those columns present fallback to the original batch insert operation.
Also, Binary/Varbinary data types also used to fail, but I fixed that part in this PR as well.