[
https://issues.apache.org/jira/browse/CALCITE-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18052681#comment-18052681
]
Zhen Chen commented on CALCITE-7359:
------------------------------------
[~nobigo] That's true, but putting it in a different .iq file doesn't work as
expected. I'm trying to handle the interactions between these tests.
> Incorrect result for array comparison with ANY operator
> -------------------------------------------------------
>
> Key: CALCITE-7359
> URL: https://issues.apache.org/jira/browse/CALCITE-7359
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.41.0
> Reporter: Zhen Chen
> Assignee: Zhen Chen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.42.0
>
>
> We can execute the following SQL in the quidem test and get a *false false*
> result, which should observe as {*}true false{*}. Although duckdb and pgsql
> do not support this syntax (they will throw an error during parsing), the
> *false false* result returned by calcite is still unacceptable.
> {code:java}
> select
> array[1,2,3]=any(array[1,2,3],array[4,2,3]),array[1,2,3]=any(array[1,3],array[4,2,3]);
> EXPR$0, EXPR$1
> false, false
> !ok {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
