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

Jin Xing edited comment on CALCITE-3387 at 12/17/19 10:37 AM:
--------------------------------------------------------------

Given tables like below
{code:java}
emp:
  empno
  deptno
  clubno

dept:
  deptno
  business

location:
  clubno
  sport
  {code}
If user write sql (multi-join) like
{code:java}
select empno, deptno, clubno, business, sport 
from emp 
  join dept using (deptno) 
  join club using (clubno){code}
What is correct behavior for Calcite ? It works find on Mysql and PostgreSql

With PR-1655, it throws Exception for ambiguous column. Do we need to support 
such case ?

 


was (Author: [email protected]):
Given tables like below
{code:java}
emp:
  empno
  deptno
  clubno

dept:
  deptno
  business

location:
  clubno
  sport
  {code}
If user write sql (multi-join) like
{code:java}
select empno, deptno, clubno, business, sport 
from emp 
  join dept using (deptno) 
  join club using (clubno){code}
What is correct behavior for Calcite ? It works find on Mysql

With PR-1655, it throws Exception for ambiguous column. Do we need to support 
such case ?

 

> Query with GROUP BY and JOIN ... USING wrongly fails with "Column 'DEPTNO' is 
> ambiguous" error
> ----------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-3387
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3387
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Chunwei Lei
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Query with GROUP BY and JOIN ... USING wrongly fails with "Column 'DEPTNO' is 
> ambiguous" error. Here is the query:
> {code}
> select deptno, count(*)
> from emp
> join dept using (deptno)
> group by deptno;
> {code}
> Because of USING, the two deptno fields should be merged into one, and 
> therefore {{deptno}} is not ambiguous. That query works in Oracle. Also note 
> that
> {code}select deptno
> from emp
> join dept using (deptno)
> {code}
> works correctly in Calcite, and has since CALCITE-2227 was fixed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to