types/json: fix an over-quoted bug in BinaryJSON.Unquote
function #11934
#12096
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.
cherry-pick #11934 to release-2.1, with little conflict-resolve
This PR tries to fix the following issue:
In current TiDB(master/3.0/2.1):
In MySQL 5.7/8.0:
What is changed and how it works?
The issue is caused by the over-unquote behaviors of
BinaryJSON.Unquote
: for a string literal of JSON, it should be unquoted only when enclosed by double quotes("
)Check List
Tests
Code changes
Side effects
N/A
Related changes
Release note
Fix an over-quoted bug for
JSON_UNQUOTE
function: only values enclosed by the double quote marks("
) should be unquoted. For example, result ofSELECT JSON_UNQUOTE("\\\\")
should be\\
(not changed).