feat(expr): cast from jsonb
to bool and number
#8008
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.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Support casting from
jsonb
scalar to smallint / int / bigint / decimal / real / double precision. It is a runtime error if the jsonb type does not match.Note that we limit the number as
f64
but PostgreSQL uses arbitrary precisionnumeric
. Thef64
is enough as suggested by RFC 8259 for good interoperability. To support higher precision, we need to enablearbitrary_precision
of crateserde_json
and exam related code path.There is also a subtle difference between decimal and f64 in PostgreSQL, when they round
2.5
to integer. But this issue is currently shadowed by #5576.Checklist
./risedev check
(or alias,./risedev c
)Documentation
Types of user-facing changes
Release note
Support casting from
jsonb
scalar to smallint / int / bigint / decimal / real / double precision. It is a runtime error if the jsonb type does not match.