From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Chris Bitmead <chris(at)bitmead(dot)com>, pgsql-hackers(at)postgreSQL(dot)org, pgsql-sql <pgsql-sql(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Re: [SQL] DISTINCT ON: speak now or forever hold your peace |
Date: | 2000-01-26 23:16:32 |
Message-ID: | 200001262316.SAA29624@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
> Chris Bitmead <chris(at)bitmead(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2000-01-26 23:46:45 | Re: OIDS (Re: [HACKERS] Well, then you keep your darn columns) |
Previous Message | Tom Lane | 2000-01-26 23:05:08 | Re: [HACKERS] Re: [SQL] DISTINCT ON: speak now or forever hold your peace |
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Bitmead | 2000-01-27 05:41:01 | Ars Digita and PostgreSQL |
Previous Message | Tom Lane | 2000-01-26 23:05:08 | Re: [HACKERS] Re: [SQL] DISTINCT ON: speak now or forever hold your peace |