[
https://issues.apache.org/jira/browse/CALCITE-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101553#comment-18101553
]
Zhen Chen commented on CALCITE-7678:
------------------------------------
https://github.com/apache/datafusion/pull/21054#issuecomment-4114934688
This refers to a previous discussion I had regarding DataFusion; I’m not sure
if it helps, but PostgreSQL documentation actually highlights the issue of
semantic inconsistency in join scenarios. DuckDB opted for its own semantics,
and DataFusion chose to align with DuckDB. Ultimately, we just need to pick a
semantic standard—I don't have a strong preference either way. Since Calcite
often looks to PostgreSQL, aligning with PostgreSQL would also be a solid
choice.
> 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
> Labels: pull-request-available
>
> 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)
