feat(expr): support unary trunc, ln, log10 (log), exp, cbrt (||/)
#9991
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?
These are the overloads in PostgreSQL:
Note that:
trunc(numeric, int)andlog(numeric, numeric)are deferred to later PRs. The binary form only handlesnumeric.expfordouble precisionhas been added in an earlier PR. This PR adds its missingnumericform.cbrtonly exists fordouble precision, althoughsqrtexists for both.pg_typeof(cbrt(1::decimal))returnsdouble precision.Checklist For Contributors
./risedev check(or alias,./risedev c)Documentation
Types of user-facing changes
Release note
support unary
trunc,ln,log10(log),exp,cbrt(||/)