[
https://issues.apache.org/jira/browse/CALCITE-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767767#comment-17767767
]
Julian Hyde commented on CALCITE-6021:
--------------------------------------
Note that the {{CURRENT_TIMESTAMP}}, {{LOCAL_TIMESTAMP}} functions are
implemented more like variables than functions. This should be similar (or
perhaps expand to existing functions).
The return type of {{CURRENT_TIMESTAMP}} may be inconsistent with the SQL
standard. If so please devise a fix.
> Add CURRENT_DATETIME function (enabled in BigQuery library)
> -----------------------------------------------------------
>
> Key: CALCITE-6021
> URL: https://issues.apache.org/jira/browse/CALCITE-6021
> Project: Calcite
> Issue Type: Bug
> Reporter: Tanner Clary
> Priority: Major
>
> Calcite supports parsing and validation for the CURRENT_DATETIME function
> according to CALCITE-4297 . However a native implementation was never added.
> The docs for the function may be found here:
>
> https://cloud.google.com/bigquery/docs/reference/standard-sql/datetime_functions#current_datetime
> An example:
> {{SELECT CURRENT_DATETIME([timezone])}} should return the current time as a
> {{DATETIME}} (a Calcite TIMESTAMP). There is an optional time zone argument.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
