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

Julian Hyde commented on CALCITE-7678:
--------------------------------------

I think that's the right approach.

I can see how Postgres needed some special semantics to deal with indexes, but 
they should have introduced syntax (something akin to {{{}PARTIAL{}}}) to 
unlock those semantics. And Calcite doesn't need to worry about indexes (except 
indirectly, when it is talking to systems like Postgres).

> Runtime equality for ROW values produces incorrect results
> ----------------------------------------------------------
>
>                 Key: CALCITE-7678
>                 URL: https://issues.apache.org/jira/browse/CALCITE-7678
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.42.0
>            Reporter: Mihai Budiu
>            Priority: Minor
>
> GROUP BY, DISTINCT, JOIN, UNION, etc by ROW-typed values produces incorrect 
> results, because ROWs are compiled to Object[] and are compared by reference 
> instead of being compared by value.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to