X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id D8D4A9DC83C for ; Tue, 7 Feb 2006 15:39:19 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 27922-08 for ; Tue, 7 Feb 2006 15:39:20 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 97B3B9DC865 for ; Tue, 7 Feb 2006 15:39:17 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k17JdHsK028041; Tue, 7 Feb 2006 14:39:17 -0500 (EST) To: gry@ll.mit.edu cc: pgsql-sql@postgresql.org Subject: Re: trecherous subselect needs warning? In-reply-to: <20060207141751.38effa97.gry@ll.mit.edu> References: <20060207120110.5d5f3c44.gry@ll.mit.edu> <27137.1139334353@sss.pgh.pa.us> <20060207141751.38effa97.gry@ll.mit.edu> Comments: In-reply-to george young message dated "Tue, 07 Feb 2006 14:17:51 -0500" Date: Tue, 07 Feb 2006 14:39:17 -0500 Message-ID: <28040.1139341157@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.108 required=5 tests=[AWL=0.108] X-Spam-Score: 0.108 X-Spam-Level: X-Archive-Number: 200602/70 X-Sequence-Number: 24080 george young writes: > How about a *documentation* suggestion that sub-queries can be > very dangerous if one doesn't qualify all column references? > Maybe with an example like the one that bit me? I have no objection to a documentation example, but there isn't any obvious place where it would fit in the manual. Perhaps some sort of "SQL gotchas" webpage on techdocs would be appropriate. regards, tom lane