Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Misnamed field in subquery does not cause error when field name exists in parent query
- From: Michael Glaesemann <grzm(at)seespotcode(dot)net>
- To: Rick Innis <rick(dot)innis(at)gmail(dot)com>
- Cc: pgsql-sql(at)postgresql(dot)org
- Subject: Re: Misnamed field in subquery does not cause error when field name exists in parent query
- Date: Sat, 22 Dec 2007 19:14:26 -0500
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
- Follow-Ups:
- References:
- Prev by Date: Misnamed field in subquery does not cause error when field name exists in parent query
- Next by Date: Re: passing a multiple join to a function?
- Previous by thread: Misnamed field in subquery does not cause error when field name exists in parent query
- Next by thread: Re: Misnamed field in subquery does not cause error when field name exists in parent query
- Indexes: