[
https://issues.apache.org/jira/browse/CALCITE-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848823#comment-17848823
]
Caican Cai edited comment on CALCITE-6312 at 5/23/24 5:57 AM:
--------------------------------------------------------------
[~njordan] Thanks for the reminder. My idea is to improve the postgres log
after merging this [PR|https://github.com/apache/calcite/pull/3789]. I hope to
find the optimal solution for calcite to adapt to these situations.
But no one has reviewed this PR yet. I still have a question. Bigquery will
also throw the same error as postgres log when log(0).
was (Author: JIRAUSER302115):
[~njordan] Thanks for the reminder. My idea is to improve the postgres log
after merging this [PR|https://github.com/apache/calcite/pull/3789]. I hope to
find the optimal solution for calcite to adapt to these situations.
> Support PostgreSQL LOG
> ----------------------
>
> Key: CALCITE-6312
> URL: https://issues.apache.org/jira/browse/CALCITE-6312
> Project: Calcite
> Issue Type: Sub-task
> Reporter: James Duong
> Assignee: Caican Cai
> Priority: Minor
>
> * We have the BigQuery implementation which has a 1-arg overload that uses
> base e (ln), and a 2-arg overload which is LOG(value, base)
> * PostgreSQL's 1-arg version uses base 10 and the 2-arg overload has the
> order reversed – LOG(base, value)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
