From: | Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | Jack Christensen <jackc(at)hylesanderson(dot)edu>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Subselect with incorrect column not a syntax error? |
Date: | 2012-04-13 18:40:46 |
Message-ID: | CANPAkgtffHq_ROxDa8i6rv5HCWGU99V-Admn8HBCNu+1h2aiAw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Indeed.
__________________________________________________________________________________
Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
Mike(dot)Blackwell(at)rrd(dot)com
http://www.rrdonnelley.com
On Fri, Apr 13, 2012 at 13:34, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Fri, Apr 13, 2012 at 11:59 AM, Jack Christensen
> <jackc(at)hylesanderson(dot)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.
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
From | Date | Subject | |
---|---|---|---|
Next Message | Phoenix Kiula | 2012-04-13 19:03:42 | Re: PGBouncer help (how to get it working) |
Previous Message | Scott Marlowe | 2012-04-13 18:35:47 | Re: Value to long for type ....: Columnname missing |