You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "duan xiong (Jira)" <ji...@apache.org> on 2021/09/03 08:26:00 UTC
[jira] [Comment Edited] (CALCITE-4756) When subquery include NULL
value, Calcite should return the right result
[ https://issues.apache.org/jira/browse/CALCITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409367#comment-17409367 ]
duan xiong edited comment on CALCITE-4756 at 9/3/21, 8:25 AM:
--------------------------------------------------------------
I run this SQL in PostgreSQL throw ERROR: operator does not exist: integer > text:
So maybe this SQL is not valid too.
was (Author: nobigo):
I run this SQL in PostgreSQL throw ERROR: operator does not exist: integer > text:
So maybe this SQL is not valid too.
> When subquery include NULL value, Calcite should return the right result
> ------------------------------------------------------------------------
>
> Key: CALCITE-4756
> URL: https://issues.apache.org/jira/browse/CALCITE-4756
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.27.0
> Reporter: duan xiong
> Assignee: duan xiong
> Priority: Major
>
> When I try to design some unit tests for CALCITE-4742. I found Calcite can't handle NULL very well in some subquery.
> For example:
> {code:java}
> select 1 in (values(null),(null))
> select 1 > some(values(null),(null))
> {code}
> This SQL should return NULL. But throw the runtime exception.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)