Use NVARCHAR to support unicode values in TEXT columns on SQLServer #5237
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
|
Looks like a duplicate of #4987. |
This was referenced Feb 3, 2022
|
I wouldn't consider this a bug. The DBAL supports Unicode to a certain extent but there's no definition of what that extent is. For instance, the recently merged #4855 was considered an improvement. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
When using the Doctrine type
textsome UTF-8 characters are converted to their ASCII equivalents. This PR uses a UTF-8 compatible column type to allow full support for UTF-8.Requires #5236 & #5235 to be merged first