[
https://issues.apache.org/jira/browse/CALCITE-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774705#comment-17774705
]
Tanner Clary edited comment on CALCITE-6021 at 10/12/23 10:03 PM:
------------------------------------------------------------------
Merged via
[db60219|https://github.com/apache/calcite/commit/db60219198442f2c60345fda95a117d379d87a61],
thanks for the help/review, [~tjbanghart] [~julianhyde]!
was (Author: JIRAUSER298151):
Merged via
[db60219|https://github.com/apache/calcite/commit/db60219198442f2c60345fda95a117d379d87a61],
thanks for the help/review, [~tjbanghart][~julianhyde]!
> 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
> Assignee: Tanner Clary
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.36.0
>
>
> 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)
