From: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: bug in 9.2.2 ? subquery accepts wrong column name : upd |
Date: | 2013-03-15 07:49:36 |
Message-ID: | 1736496.2mMupsnC8K@smadev.internal.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Thanx Tom.
On Πεμ 14 ÎÎ±Ï 2013 12:17:46 Tom Lane wrote:
> Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> writes:
> > dynacom=# SELECT DISTINCT ON (qry.setid) qry.setid, qry.arragg[1:2] FROM
> > (select distinct sst.setid,(array_agg(vsl.name) OVER (PARTITION BY sst.setid ORDER BY character_length(vsl.name))) as arragg
> > FROM sissets sst, vessels vsl WHERE vsl.id=sst.vslid ORDER BY sst.setid) as qry
> > WHERE array_length(qry.arragg,1)>1 AND qry.setid IN (SELECT setid from sis_oper_cons) ORDER BY qry.setid,array_length(qry.arragg,1);
> > [ works ]
>
> > however, there is not column setid in sis_oper_cons,
>
> If not, that's a perfectly legal outer reference to qry.setid.
>
> Probably not one of SQL's better design features, since it confuses
> people regularly; but it's required by spec to work like that.
>
> regards, tom lane
>
>
>
-
Achilleas Mantzios
IT DEV
IT DEPT
Dynacom Tankers Mgmt
From | Date | Subject | |
---|---|---|---|
Next Message | Victor Sterpu | 2013-03-16 19:50:31 | ZIP function |
Previous Message | Tom Lane | 2013-03-15 03:15:17 | Re: UPDATE query with variable number of OR conditions in WHERE |