From: | "Edward Q(dot) Bridges" <ed(dot)bridges(at)buzznik(dot)com> |
---|---|
To: | "Jules Bean" <jules(at)jellybean(dot)co(dot)uk>, "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Is this proper UNION behavior?? |
Date: | 2000-11-14 15:39:22 |
Message-ID: | 200011141544.eAEFiPs43659@mail.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)bridges(at)buzznik(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Hervé Piedvache | 2000-11-14 16:01:22 | Error with Vaccum Analyze !? |
Previous Message | Anders R. Sveen | 2000-11-14 15:24:58 | Encoding |