[
https://issues.apache.org/jira/browse/CALCITE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16933207#comment-16933207
]
Danny Chan commented on CALCITE-1178:
-------------------------------------
[~jacobroldan], yeah, you are right, 1.21 supports implicit type coercion for
DATE and TIMESTAMP in binary comparison, i think we can support between either.
For current coercion rules, for "date > timestamp", we coerce the DATE to
TIMESTAMP.
[~julianhyde] I have checked MYSQL 5.6 and PostgreSQL 9.6, they have the same
behavior with Calcite.
> Allow SqlBetweenOperator to compare DATE and TIMESTAMP
> ------------------------------------------------------
>
> Key: CALCITE-1178
> URL: https://issues.apache.org/jira/browse/CALCITE-1178
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Sean Hsuan-Yi Chu
> Assignee: Sean Hsuan-Yi Chu
> Priority: Major
>
> An expression such as
> {code}
> date '1999-03-02' between date '1999-03-01' and timestamp '1999-03-03
> 00:00:00.0'
> {code}
> will incur SqlValidatorException since SqlBetweenOperator does not allow DATE
> and TIMESTAMP comparison. In terms of usability, it would be great if this
> type of comparison is allowed in Calcite.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
