[jira] [Commented] (CALCITE-4297) Babel should accept CURRENT_DATE and CURRENT_DATETIME

["Julian Hyde (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209830#comment-17209830 ] 

Julian Hyde commented on CALCITE-4297:
--------------------------------------

This is duplicate of CALCITE-1766, which added {{SqlConformance.allowNiladicParentheses()}}. Maybe the value needs to be changed for {{SqlConformanceEnum.BIG_QUERY}}.

> Babel should accept CURRENT_DATE and CURRENT_DATETIME
> -----------------------------------------------------
>
>                 Key: CALCITE-4297
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4297
>             Project: Calcite
>          Issue Type: Bug
>          Components: babel
>    Affects Versions: 1.25.0
>            Reporter: Justin Swett
>            Priority: Major
>
> The following BigQuery SQL contains CURRENT_DATE and CURRENT_DATETIME without parentheses. Babel parser should accept it. (It should also accept CURRENT_TIME and CURRENT_TIMESTAMP with parentheses.)
>  
> The following SQL should trigger *CalciteContextException: No match found for function signature CURRENT_TIMESTAMP()* for the date functions, or if you add parens to the current_time.
>  
> {code:java}
> WITH THE_TIMES_ARE_STATIC AS
> (SELECT
>     CURRENT_DATE as a_date,
>     CURRENT_DATETIME() as a_datetime,
>     CURRENT_TIME as a_time,
>     CURRENT_TIMESTAMP() as a_timestamp
> )
> SELECT * FROM THE_TIMES_ARE_STATIC 
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)