[5.8] Unquote JSON values on MySQL #25732
Merged
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.
Among the four supported databases, only the MySQL implementation returns quoted JSON values:
#24817 added the
->>
operator that returns unquoted values. But this doesn't change the default behavior and is incompatible with the other databases (#25726): If your application expects unquoted values on MySQL and PostgreSQL, you have to detect the database and then use'options->>language'
or'options->language'
.I think the MySQL implementation should be consistent with the other databases and return unquoted values by default. I would argue that an unquoted value is the result a user expects.
As a breaking change, this targets 5.8.