Re: [HACKERS] Oops, I seem to have changed UNION's behavior - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: [HACKERS] Oops, I seem to have changed UNION's behavior
Date
Msg-id 3735A41D.3EE1073D@alumni.caltech.edu
Whole thread Raw
In response to Re: [HACKERS] Oops, I seem to have changed UNION's behavior  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] Oops, I seem to have changed UNION's behavior  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [HACKERS] Oops, I seem to have changed UNION's behavior  (Taral <taral@taral.net>)
List pgsql-hackers
> > Am I right in thinking that UNION (without ALL) is defined to do a
> > DISTINCT on its result, so that duplicates are removed even if the
> > duplicates both came from the same source table?  That's what 6.4.2
> > does, but I do not know if it's strictly kosher according to the SQL
> > spec.

(Just in case this is still active)

Yes, this is the right behavior according to SQL92...
                        - Thomas

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Problem with complex query
Next
From: Dmitry Samersoff
Date:
Subject: Problem installing plpgsql