Use JSON_VALUE() for scalar JSON values if available or workaround weird JSON_EXTRACT() behavior in regards to null otherwise#1899
Open
lauxjpn wants to merge 2 commits intoPomeloFoundation:mainfrom
Open
Conversation
…ird JSON_EXTRACT() behavior otherwise.
|
What steps are needed to move this PR forward? |
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
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.
We will use
JSON_VALUE()for scalar JSON values from now on, because it seems to handlenullvalues correctly.JSON_EXTRACT()will return a string with the contents ofnullfor a JSONnullvalue instead of a SQLNULLvalue (see Bug #85755: JSON containing null value is extracted as a string "null").So when we have to depend on
JSON_EXTRACT(), we have to explicitly check for that specific case to ensure that the expected value is returned.Fixes #1897