Re: Subselect with incorrect column not a syntax error? - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Subselect with incorrect column not a syntax error?
Date
Msg-id CAOR=d=3dRXAHxhvHh6-VYJb9a0r6redL1s13GzJuiNAX+q28aA@mail.gmail.com
Whole thread Raw
In response to Re: Subselect with incorrect column not a syntax error?  (Jack Christensen <jackc@hylesanderson.edu>)
Responses Re: Subselect with incorrect column not a syntax error?  (Mike Blackwell <mike.blackwell@rrd.com>)
List pgsql-general
On Fri, Apr 13, 2012 at 11:59 AM, Jack Christensen
<jackc@hylesanderson.edu> wrote:
> On 4/13/2012 11:39 AM, Mike Blackwell wrote:
>>
>> Could someone please explain to me why the following select does not
>> result in a syntax error?  (9.0.3)
>>
>> begin;
>>
>> create table x( c1 integer , c2 integer);
>> create table y( c3 integer, c4 integer);
>>
>> select * from x where c2 in ( select c2 from y where c4 = 2 );
>>
>>
>> rollback;
>>
>> Mike
>>
> Your subquery is correlated with the outer query. So the c2 in the subquery
> is referring to table x.

This is a good example of why one should always use a table alias
prefix when using subqueries.

pgsql-general by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: Value to long for type ....: Columnname missing
Next
From: Scott Marlowe
Date:
Subject: Re: Value to long for type ....: Columnname missing