Json function Improvements #1506
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
Parallel Test execution Gradle Caching Explicitly request for latest JavaCC 7.0.10
Parallel Test execution Gradle Caching Explicitly request for latest JavaCC 7.0.10
Space around the `:` delimiter of JSON Functions
Enforce `KEY` as `S_CHAR_LITERAL` Allow `Column` as `VALUE` Temporarily disable Postgres Syntax
Bring back Postgres Syntax Enable MySQL Syntax JSON_OBJECT(key, value [, key, value, ...]) Fix some more tests, where key was not a String
wumpz
reviewed
Apr 9, 2022
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.
Fixes #1504
Correct parsing the Standard Compliant
JSON_OBJECT()function, whereKEYis supposed to be a StringAdd support for MySQL
JSON_OBJECT(), where multiple Key-Value Pairs are separated by Comma,