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: Rick Innis <rick(dot)innis(at)gmail(dot)com>
- To: Michael Glaesemann <grzm(at)seespotcode(dot)net>
- 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: Mon, 24 Dec 2007 14:25:33 -0500
On 22-Dec-07, at 7:14 PM, Michael Glaesemann 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.
Ow. Thanks for confirming both my suspicions and my fears :-) R.
- References:
- Prev by Date: Re: slow query - only uses indices
- Next by Date: Advice for generalizing trigger functions
- Previous by thread: Re: Misnamed field in subquery does not cause error when field name exists in parent query
- Next by thread: returning an array as a list fo single-column rows?
- Indexes: