feat: add JSON_LENGTH built-in function - #24469
Merged
Merged
Conversation
ULookup
requested review from
XuPeng-SH,
aunjgr,
fengttt,
heni02 and
ouyuanning
as code owners
May 19, 2026 08:25
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
|
Add test cases for three previously untested branches: - First arg that cannot cast to varchar (T_geometry) fails - Second arg castable to varchar (T_int64) succeeds with cast - Second arg not castable to varchar (T_geometry) fails
Coverage: all 14 edge cases including NULL, object/array counts, scalar handling, boolean literals, path extraction, and error cases.
Contributor
Merge Queue Status
This pull request spent 25 seconds in the queue, including 5 seconds running CI. Required conditions to merge
|
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
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.
What type of PR is this?
Which issue(s) this PR fixes:
issue #23140
What this PR does / why we need it:
Add
JSON_LENGTH(json_doc[, path])built-in function, matching MySQL behavior:JSON_EXTRACTImplementation follows the existing JSON function pattern (
jsonExtract), including a dedicatedjsonLengthCheckFnfor argument validation andjsonLengthoperator for execution.