Support Unicode in SQL Server BULK INSERT statements. #152
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
|
Works with minor changes. Note does not fix #79; required bulk loader format (.fmt) files to be changed from SQL |
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.
As discussed in #79. Note that I have just added
DATAFILETYPE = 'widechar'clauses to theWITHblocks of all theBULK INSERTstatements.Turns out we use them a lot. There are SQL scripts, Java classes and JavaScript files. Also at least one C++ file. I don't even know what that's doing there, but it didn't need to change, luckily.
Note that I haven't tested this.