You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Rui Wang (Jira)" <ji...@apache.org> on 2019/11/21 18:22:00 UTC
[jira] [Commented] (CALCITE-3528) TIMESTAMPADD/TIMESTAMPDIFF can't
handle unit of MILLISECOND
[ https://issues.apache.org/jira/browse/CALCITE-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979479#comment-16979479 ]
Rui Wang commented on CALCITE-3528:
-----------------------------------
I am thinking it was just an implementation decision (e.g. didn't implement that). Some other systems supports unit of millisecond. For example, see BigQuery's doc: https://cloud.google.com/bigquery/docs/reference/standard-sql/timestamp_functions#timestamp_diff
> TIMESTAMPADD/TIMESTAMPDIFF can't handle unit of MILLISECOND
> -----------------------------------------------------------
>
> Key: CALCITE-3528
> URL: https://issues.apache.org/jira/browse/CALCITE-3528
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.21.0
> Reporter: Zhenghua Gao
> Priority: Minor
>
> Calcite's SQL parser can't handle unit of MILLISECOND for TIMESTAMPADD/TIMESTAMPDIFF functions. And I checked MySql[1], which can't handle unit of MILLISECOND too.
> Is there any reason to not support unit of MILLISECOND of the two function?
> [1] [https://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#function_timestampadd]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)