Hi,

SQL92 seems to assume that results of the INTERSECT/EXCEPT contain no
duplications unless "ALL" is specified. However PostgreSQL 6.5.1 does
not follow the requirement, I think. Maybe we need to add this to the
TODO list?
---
Tatsuo Ishii


Thu, 05 Aug 1999 10:13:59 +0900
Tatsuo Ishii <t-ishii@sra.co.jp>
INTERSECT/EXCEPT and duplicates?
> Hi,
> 
> SQL92 seems to assume that results of the INTERSECT/EXCEPT contain no
> duplications unless "ALL" is specified. However PostgreSQL 6.5.1 does
> not follow the requirement, I think. Maybe we need to add this to the
> TODO list?
> ---

Added to TODO:

* have INTERSECT/EXCEPT prevent duplicates unless ALL is specified

-- 
  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

Wed, 4 Aug 1999 21:44:35 -0400 (EDT)
Bruce Momjian <maillist@candle.pha.pa.us>
Re: [HACKERS] INTERSECT/EXCEPT and duplicates?
Tatsuo Ishii <t-ishii@sra.co.jp> writes:
> SQL92 seems to assume that results of the INTERSECT/EXCEPT contain no
> duplications unless "ALL" is specified. However PostgreSQL 6.5.1 does
> not follow the requirement, I think.

I think you are right --- the ALL keyword is only implemented for UNION
(and it's not quite right there either :-().  For the other two, you
just get whichever behavior was easiest to implement, I suppose...

			regards, tom lane

Thu, 05 Aug 1999 10:09:37 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] INTERSECT/EXCEPT and duplicates? 