Fix collation conflict #18
Merged
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
Owner
|
@simelis Interesting…Thanks for the PR! 👍 I’ll run the integration tests to confirm everything is consistent! |
cajuncoding
approved these changes
Mar 22, 2024
Owner
cajuncoding
left a comment
cajuncoding
left a comment
There was a problem hiding this comment.
Changes look Good, and all integration tests pass on the first run!
PR Approved ✅
Thanks for the Contribution to make this better for everyone 🙏
Owner
|
Integration Tests look good ✅ |
Owner
|
Now available in v2.4.4 on Nuget: https://www.nuget.org/packages/SqlBulkHelpers/2.4.4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The QueryDBTableSchema* queries result in the following exception when my db and temp db collations do not match:
Cannot resolve the collation conflict between "tempdb_collation" and "my_db_colletion" in the equal to operation.This fixes the error. I didn't test with temp tables though.