You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2014/08/15 19:21:18 UTC

[jira] [Commented] (OPTIQ-373) NOT IN and NULL values

    [ https://issues.apache.org/jira/browse/OPTIQ-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098775#comment-14098775 ] 

Julian Hyde commented on OPTIQ-373:
-----------------------------------

Note that the SQL standard does not allow "bare" nulls because their type cannot be deduced. (It does allow 'insert into ... select null ...'.) Your case workaround works; also note that 'cast(null as <type>)' works fine.

> NOT IN and NULL values
> ----------------------
>
>                 Key: OPTIQ-373
>                 URL: https://issues.apache.org/jira/browse/OPTIQ-373
>             Project: Optiq
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>         Attachments: OPTIQ-373.1.patch
>
>
> Write a test to check that NOT IN evaluates to true, and therefore returns all rows, if the sub-query returns a null.
> Fix if necessary.
> Also test composite keys.



--
This message was sent by Atlassian JIRA
(v6.2#6252)