[
https://issues.apache.org/jira/browse/CALCITE-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848707#comment-17848707
]
Norman Jordan commented on CALCITE-5634:
----------------------------------------
The PR linked above only makes the *GREATEST* and *LEAST* functions available
in the PostgreSQL library. It doesn't alter the behaviour of them to match
PostgreSQL (ie. only return null when all arguments are null).
Is it important to match the behaviour of PostgreSQL?
> Enable GREATEST, LEAST functions in PostgreSQL library
> ------------------------------------------------------
>
> Key: CALCITE-5634
> URL: https://issues.apache.org/jira/browse/CALCITE-5634
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.34.0
> Reporter: Dmitry Sysolyatin
> Assignee: Dmitry Sysolyatin
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The LEAST and GREATEST functions have been implemented for BigQuery and
> Oracle, but haven't been added for PostgreSQL. PostgreSQL supports LEAST,
> GREATEST as well [1].
> Also PostgreSQL's LEAST, GREATEST functions behave differently with NULL
> values than ORACLE or BigQuery.
> From PostgreSQL documentation [1]:
> ??The result will be NULL only if all the expressions evaluate to NULL.??
> From BigQuery documentation [2]:
> ??They return NULL if any of the input parameters is NULL.??
> [1]
> [https://www.postgresql.org/docs/15/functions-conditional.html#FUNCTIONS-GREATEST-LEAST]
> [2]
> [https://cloud.google.com/bigquery/docs/reference/standard-sql/mathematical_functions]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
