From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Chris Bitmead <chris@bitmead.com>
Cc: pgsql-hackers@postgreSQL.org, pgsql-sql <pgsql-sql@postgreSQL.org>
Subject: Re: [HACKERS] Re: [SQL] DISTINCT ON: speak now or forever hold your peace
Date: Wed, 26 Jan 2000 18:16:32 -0500 (EST)
Message-ID: <200001262316.SAA29624@candle.pha.pa.us> (raw)
In-Reply-To: <19434.948927908@sss.pgh.pa.us>
> Chris Bitmead <chris@bitmead.com> writes:
> > As long as we're fixing the syntax, I'm wondering if it wouldn't be more
> > logical to have DISTINCT ON somewhere later in the syntax.
>
> Well, SELECT DISTINCT is that way because SQL92 says so. Putting the
> DISTINCT ON variant somewhere else might be logically purer, but I think
> it'd be confusing.
>
> Also, isn't the reason we have DISTINCT ON at all that it's there to
> be compatible with MySQL or someone? I figured adding parens would be
> about the least-surprising variant syntax for a person used to those
> other products.
>
Makes sense to me.
--
Bruce Momjian | http://www.op.net/~candle
pgman@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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, chris@bitmead.com
Subject: Re: [HACKERS] Re: [SQL] DISTINCT ON: speak now or forever hold your peace
In-Reply-To: <200001262316.SAA29624@candle.pha.pa.us>
References: <19434.948927908@sss.pgh.pa.us> <200001262316.SAA29624@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox