Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA66117 for ; Wed, 18 Aug 1999 11:16:15 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id LAA02000; Wed, 18 Aug 1999 11:10:39 -0400 (EDT) From: Bruce Momjian Message-Id: <199908181510.LAA02000@candle.pha.pa.us> Subject: Re: [SQL] Using intersect in subquery In-Reply-To: <24554.934984289@sss.pgh.pa.us> from Tom Lane at "Aug 18, 1999 09:51:29 am" To: Tom Lane Date: Wed, 18 Aug 1999 11:10:38 -0400 (EDT) CC: Hamid Khoshnevis , pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > >> (I believe) I am running PG 6.4. The INTERSECT by itself works, but not in > >> a subquery. > >> > > No, it still won't work --- the current grammar specifies SubSelect not > select_clause as the kind of select you can put inside an expression. > Not sure what it would take to fix this; I have a feeling that just > changing the grammar wouldn't be good enough :-(. Better add it to the > TODO list: > * Support UNION/INTERSECT/EXCEPT in sub-selects Done. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026