Re: [SQL] Misnamed field in subquery does not cause error when field name exists in parent query

On Dec 22, 2007, at 17:12 , Rick Innis wrote: It may be that SQL is doing exactly as it should, since 'id' is in scope within the subselect, but if that's the case it's a nasty gotcha. Yes, and yes. Michael Glaesemann grzm seespotcode net ---(end of broadcast)-

[SQL] Misnamed field in subquery does not cause error when field name exists in parent query

Wondering if this is actually a bug, before I file a bug report on it. Consider this sequence: =# create table public.test1 (id int); CREATE TABLE =# create table public.test2 (it int); CREATE TABLE =# select * from test1 where id in (select id from test2); id (0 rows) Note that the sele