MSSQLSpatial: Don't truncate string values #844
Merged
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
On UNIX and other systems where the size of "wchar_t" is greater than two bytes, shorten the length of each charater in a wide-character string before passing it to the ODBC driver so the string is not truncated.
ghost
deleted the
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.
What does this PR do?
Modify
OGRMSSQLSpatialTableLayer::AppendFieldValue()to shorten, on UNIX and other systems where the size ofwchar_tis greater than two bytes, the length of each character in a wide-character string before passing it on to the ODBC driver so a string field's value is not truncated.What are related issues/pull requests?
Fixes #843.
Tasklist
Environment
Provide environment details, if relevant: