pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Herouth Maoz <herouth@oumail.openu.ac.il>
To: Hamid Khoshnevis <hamid@emarq.com>
To: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Using intersect in subquery
Date: Wed, 18 Aug 1999 17:21:39 +0300
Message-ID: <l03130302b3e070154f3d@[147.233.159.109]> (raw)
In-Reply-To: <24554.934984289@sss.pgh.pa.us>
References: <199908180238.WAA12634@candle.pha.pa.us>

At 16:51 +0300 on 18/08/1999, Tom Lane wrote:


> Bruce Momjian <maillist@candle.pha.pa.us> writes:
> > Try 6.5.  We fixed some Intersect stuff.
> >>
> >> select * from Table1
> >> where KeyField1 in
> >> (select KeyField2 from Table2 where  somecondition
> >> intersect
> >> select KeyField3 from Table3  where somecondition);
> >>
> >> (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

In the meantime I suppose changing the query might work. Intersect should
return only the rows which are returned from both tables, but since we are
talking about only one field here, it may be convenient to just do an
internal join?

SELECT * FROM Table1
WHERE KeyField in
(  SELECT Keyfield2
   FROM Table2, Table3
   WHERE Keyfield2 = Keyfield3
);

This is not equivalent in the case of a NULL, but in all other cases, I
believe it is.

Or maybe the following is more efficient (and clear?):

SELECT * FROM Table1
WHERE EXISTS
(  SELECT *
   FROM Table2
   WHERE KeyField2 = KeyField
)
AND EXISTS
(  SELECT *
   FROM Table3
   WHERE KeyField3 = KeyField
);

Herouth

--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma





view thread (7+ messages)  latest in thread

Message-ID: <l03130302b3e070154f3d@[147.233.159.109]>
Permalink:  ../l03130302b3e070154f3d@%5B147.233.159.109%5D/
Also on:    postgresql.org/message-id/l03130302b3e070154f3d@[147.233.159.109]

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: herouth@oumail.openu.ac.il, hamid@emarq.com
  Subject: Re: [SQL] Using intersect in subquery
  In-Reply-To: <l03130302b3e070154f3d@[147.233.159.109]>
  References: <199908180238.WAA12634@candle.pha.pa.us> <l03130302b3e070154f3d@[147.233.159.109]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox