Re: correlated delete with 'in' and 'left outer join' - Mailing list pgsql-general

From Michael Chaney
Subject Re: correlated delete with 'in' and 'left outer join'
Date
Msg-id 20040227170110.GA7898@michaelchaney.com
Whole thread Raw
In response to Re: correlated delete with 'in' and 'left outer join'  (Mike Mascari <mascarm@mascari.com>)
Responses Re: correlated delete with 'in' and 'left outer join'  (Mike Mascari <mascarm@mascari.com>)
List pgsql-general
> >The original subquery looked like:
> >select distinct e.ItemID from LogEvent e left outer join Item i
> >on e.ItemID = i.ItemID where e.EventType != 'i' and i.ItemID is null

Please, before continuing this thread, read my post below.  What you're
all getting around to, albeit painfully, is that this subquery is
worthless as-is.  This is the mysql way of finding rows in one table
with no match in another without the convenience of the "in" or "exists"
constructs.

Because we're using Postgres and have those constructs, the original
query can be rewritten simply with either:

delete from LogEvent where EventType != 'i' and ItemID not in
        (select ItemID from Item)

That's it.  That's the whole query.  It does what he wants.

Michael
--
Michael Darrin Chaney
mdchaney@michaelchaney.com
http://www.michaelchaney.com/

pgsql-general by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: field must appear in the GROUP BY clause or be used
Next
From: Richard Huxton
Date:
Subject: Re: field must appear in the GROUP BY clause or be used