[
https://issues.apache.org/jira/browse/CALCITE-6186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803314#comment-17803314
]
Julian Hyde commented on CALCITE-6186:
--------------------------------------
Does this change cover incoming SQL (i.e. SqlLibraryOperators) or outgoing SQL
(RelToSql), or both?
It's probably better that commits do in or out, not both. On the 'out' side, I
wish we had a more systematic approach (e.g. a mapping table). Or maybe we need
a bidirectional mapping that is not tied to 'in' or 'out'.
> Enable DATEDIFF for Snowflake, map to BigQuery equivalents
> ----------------------------------------------------------
>
> Key: CALCITE-6186
> URL: https://issues.apache.org/jira/browse/CALCITE-6186
> Project: Calcite
> Issue Type: Improvement
> Reporter: Tanner Clary
> Assignee: Tanner Clary
> Priority: Major
>
> (Any suggestions for a better title would be helpful).
> Snowflake supports the DATEDIFF function:
> https://docs.snowflake.com/en/sql-reference/functions/datediff
> This is equivalent to the BigQuery TIMESTAMP/TIME/DATE/DATETIME_DIFF
> functions according to:
> https://cloud.google.com/bigquery/docs/migration/snowflake-sql#date_and_time_functions
> The operands are reorder but otherwise the functions operate similarly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
