From: Tom Lane <tgl@sss.pgh.pa.us>
To: 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:05:08 -0500
Message-ID: <19434.948927908@sss.pgh.pa.us> (raw)
In-Reply-To: <388F7AE9.EDD10859@bitmead.com>
References: <B4B3546E.5A80%jscarfe@callnetuk.com>
<13995.948820606@sss.pgh.pa.us>
<388F7AE9.EDD10859@bitmead.com>
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.
regards, tom lane
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: 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: <19434.948927908@sss.pgh.pa.us>
References: <B4B3546E.5A80%jscarfe@callnetuk.com> <13995.948820606@sss.pgh.pa.us> <388F7AE9.EDD10859@bitmead.com> <19434.948927908@sss.pgh.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