[
https://issues.apache.org/jira/browse/CALCITE-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956748#comment-17956748
]
Xiong Tenghui edited comment on CALCITE-7051 at 6/8/25 2:35 AM:
----------------------------------------------------------------
NATURAL JOIN is not the case issue, it is because that the method
"expandExprFromJoin" does not handle the NATURAL JOIN in this case.
[https://github.com/apache/calcite/blob/main/core/src/main/java/org/apache/calcite/sql/validate/SqlValidatorImpl.java#L529]
was (Author: JIRAUSER309962):
NATURAL JOIN is not the case issue, it is because that the method
"expandExprFromJoin" does not handle the NATURAL JOIN in this case.
> JOIN with USING does not match the appropriate columns when caseSensitive is
> false
> ----------------------------------------------------------------------------------
>
> Key: CALCITE-7051
> URL: https://issues.apache.org/jira/browse/CALCITE-7051
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Xiong Tenghui
> Assignee: Xiong Tenghui
> Priority: Minor
> Labels: pull-request-available
>
> In JOIN ... USING, if have set caseSensitive as false(and
> quotedCasing,unquotedCasing=CHANGED), common columns should be success
> regardless of case. For example, the following 4 queries are valid on Presto,
> and both of them maybe failed, it depends on the case of column name in
> catalog. In each case, {{DEPTNO}} is the common column.
>
> {code:java}
> select DEPTNO from emp join dept using (DEPTNO);
> select deptno from emp join dept using (deptno);
> select DEPTNO from emp join dept using (deptno);
> select deptno from emp join dept using (DEPTNO); {code}
> I think it is because that caseSensitive is not handled well in the
> following method.
> https://github.com/apache/calcite/blob/main/core/src/main/java/org/apache/calcite/sql/validate/SqlValidatorImpl.java#L529
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
