[
https://issues.apache.org/jira/browse/CALCITE-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384551#comment-17384551
]
duan xiong edited comment on CALCITE-4486 at 7/21/21, 1:55 AM:
---------------------------------------------------------------
After doing some research and describe in
[unique-predicate|https://www.jooq.org/doc/3.0/manual/sql-building/conditional-expressions/unique-predicate/].
I decide The UNIQUE predicts support project more than 1 field in the
subquery. and the filter becomes:
{code:java}
WHERE ($1) IS NOT NULL and ($2) IS NOT NULL{code}
The PR will be submitted in the next few days
was (Author: nobigo):
After doing some research and describe in
[unique-predicate|https://www.jooq.org/doc/3.0/manual/sql-building/conditional-expressions/unique-predicate/].
I decide The UNIQUE predicts support project more than 1 field in the
subquery. and the filter becomes:
WHERE ($1) IS NOT NULL and ($2) IS NOT NULL
The PR will be submitted in the next few days
> UNIQUE predicate
> ----------------
>
> Key: CALCITE-4486
> URL: https://issues.apache.org/jira/browse/CALCITE-4486
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: duan xiong
> Priority: Major
>
> Implement the UNIQUE predicate, as specified by the SQL standard.
> Example:
> {code:java}
> UNIQUE (SELECT publishedIn FROM Book
> WHERE authorId = 3)
> NOT UNIQUE (SELECT publishedIn FROM BOOK
> WHERE authorId = 3)
> {code}
> {{UNIQUE}} returns {{FALSE}} if the query returns two or more rows that do
> not include NULL values and are equal. Like {{EXISTS}}, it never returns
> {{UNKNOWN}}.
> More details at
> [JOOQ|https://www.jooq.org/doc/3.0/manual/sql-building/conditional-expressions/unique-predicate/].
> This Issue support the UNIQUE predicate by set {{isExpand}} to return false,
> so sub-queries are converted to {{RexSubQuery}} expressions and handled later
> by {{SubQueryRemoveRule}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
