[ 
https://issues.apache.org/jira/browse/CALCITE-7629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mihai Budiu updated CALCITE-7629:
---------------------------------
    Description: 
The parser uses SqlStdOperatorTable.DATEDIFF to represent TIMETSAMPDIFF In 
consequence, programs that use TIMETSAMPDIFF  will actually unparse as 
DATEDIFF, and will report errors about DATEDIFF, e.g.:

SELECT(TIMESTAMP_DIFF(a, b)) FROM T

will produce an error message like:

Invalid number of arguments to function 'DATEDIFF'. Was expecting 3 arguments

This is confusing for the users.

  was:
The parser uses SqlStdOperatorTable.TIMESTAMP_DIFF to represent DATEDIFF. In 
consequence, programs that use DATEDIFF will actually unparse as TIMESTAMPDIFF, 
and will report errors about TIMESTAMPDIFF, e.g.:

SELECT(DATEDIFF(a, b)) FROM T

will produce an error message like:

Invalid number of arguments to function 'TIMESTAMPDIFF'. Was expecting 3 
arguments

This is confusing for the users.


> TIMESTAMPDIFF is shown in error messages as DATEDIFF
> ----------------------------------------------------
>
>                 Key: CALCITE-7629
>                 URL: https://issues.apache.org/jira/browse/CALCITE-7629
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.42.0
>            Reporter: Mihai Budiu
>            Priority: Minor
>
> The parser uses SqlStdOperatorTable.DATEDIFF to represent TIMETSAMPDIFF In 
> consequence, programs that use TIMETSAMPDIFF  will actually unparse as 
> DATEDIFF, and will report errors about DATEDIFF, e.g.:
> SELECT(TIMESTAMP_DIFF(a, b)) FROM T
> will produce an error message like:
> Invalid number of arguments to function 'DATEDIFF'. Was expecting 3 arguments
> This is confusing for the users.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to