RE: [SQL] Why *no* ambig.uous complain in select part?

From: "Edward W(dot) Rouse" <erouse(at)comsquared(dot)com>
To: <pgsql-sql(at)postgresql(dot)org>
Subject: RE: [SQL] Why *no* ambig.uous complain in select part?
Date: 2008-08-22 20:44:14
Message-ID: 018501c90497$d6c7f050$8457d0f0$@com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Just a guess, but it seems to me that since the join is using col1 and col2
there is no ambiguity. They should be the same no matter which table it
comes from.

Edward W. Rouse

-----Original Message-----
From: pgsql-sql-owner(at)postgresql(dot)org [mailto:pgsql-sql-owner(at)postgresql(dot)org]
On Behalf Of Emi Lu
Sent: Friday, August 22, 2008 4:12 PM
To: pgsql-sql(at)postgresql(dot)org
Subject: [SQL] Why *no* ambig.uous complain in select part?

Good morning,

Just notice one small thing, and need your information about select

select col1, col2
from table1
left join table2
using (col1, col2)

;

This query never complain about ambiguous columns of col1 and col2 in
the select part.

My guess is:
(1) col1, col2 always return table1.col1, table1.col2
(2) because using (col1, col2)
that's why, table name is not necessary in select part

Am I wrong? Please advise?

Thank you!

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Emi Lu 2008-08-22 20:48:42 Re: RE: [SQL] Why *no* ambig.uous complain in select part?
Previous Message Emi Lu 2008-08-22 20:12:14 Why *no* ambig·uous complain in select part?