Re: Is this proper UNION behavior?? - Mailing list pgsql-general

From Edward Q. Bridges
Subject Re: Is this proper UNION behavior??
Date
Msg-id 200011141544.eAEFiPs43659@mail.postgresql.org
Whole thread Raw
In response to Is this proper UNION behavior??  ("Edward Q. Bridges" <ed.bridges@buzznik.com>)
List pgsql-general
On Tue, 14 Nov 2000 13:35:14 +0000, Jules Bean wrote:

> On Mon, Nov 13, 2000 at 10:12:39PM -0500, Tom Lane wrote:
> > "Edward Q. Bridges" <ed.bridges@buzznik.com> writes:
> > > ebridges=> (select * from has_some_dupes)
> > > ebridges-> UNION
> > > ebridges-> (select * from has_some_dupes);
> >
> > [ produces the same result as "select * from has_some_dupes" ]
> >
> Of course, the real bug here is in SQL, namely that it allows
> duplicates in tables.
>

given the presence of SELECT DISTINCT and unique constraints, i
wouldn't consider it a bug in SQL.  probably better anyway to have
the flexibility of having duplicates in a table, while providing the
ability to constrain to unique tuples if necessary.










pgsql-general by date:

Previous
From: "Anders R. Sveen"
Date:
Subject: Encoding
Next
From: Hervé Piedvache
Date:
Subject: Error with Vaccum Analyze !?