[
https://issues.apache.org/jira/browse/CALCITE-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16955806#comment-16955806
]
Julian Hyde commented on CALCITE-3433:
--------------------------------------
I wonder if the TIMESTAMP value is being stored as a Long (rather than long)
because it is nullable, and we are using == to compare rather than
Object.equals.
> EQUALS operator between date/timestamp types returns false if the type is
> nullable
> ----------------------------------------------------------------------------------
>
> Key: CALCITE-3433
> URL: https://issues.apache.org/jira/browse/CALCITE-3433
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.17.0, 1.18.0, 1.19.0, 1.20.0, 1.21.0
> Reporter: jiezouSH
> Priority: Major
>
> sql
> select time0=time1 from (select timestamp'2000-12-30 21:07:32'as
> time0,timestamp'2000-12-30 21:07:32'as time1 union all select cast(null as
> timestamp) as time0,cast(null as timestamp) as time1) calcs
> answer is false
> but
> sql
> select time0=time1 from (select timestamp'2000-12-30 21:07:32'as
> time0,timestamp'2000-12-30 21:07:32'as time1) calcs
> answer is true
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
