pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <maillist@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Hannu Krosing <hannu@trust.ee>
Cc: hackers@postgreSQL.org
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Re: [HACKERS] SELECT DISTINCT question
Date: Thu, 23 Sep 1999 13:18:18 -0400 (EDT)
Message-ID: <199909231718.NAA19629@candle.pha.pa.us> (raw)
In-Reply-To: <24413.931901508@sss.pgh.pa.us>

Tom, any status on this DISTINCT ON ripout?


> Hannu Krosing <hannu@trust.ee> writes:
> >> "DISTINCT will eliminate all duplicate rows from the selection.
> >> DISTINCT ON column will eliminate all duplicates in the specified column;
> >> this is equivalent to using GROUP BY column."
> 
> > If it is equivalent to GROUP BY then it should allow only aggregates 
> > in non-distinct columns, like:
> > select distinct on date date, sum(bytes) from access_log;
> > If it does not, then it should be files as a bug imho.
> 
> It does not.  Whether that is a bug is hard to say, since there is no
> standard I know of that says what it *is* supposed to do.
> 
> If you look at the select_distinct_on regress test outputs, I bet you
> will be even less happy:
> 
> QUERY: SELECT DISTINCT ON string4 two, string4, ten
> 	   FROM tmp
>    ORDER BY two using <, string4 using <, ten using <;
> two|string4|ten
> ---+-------+---
>   0|AAAAxx |  0
>   0|HHHHxx |  0
>   0|OOOOxx |  0
>   0|VVVVxx |  0
>   1|AAAAxx |  1
>   1|HHHHxx |  1
>   1|OOOOxx |  1
>   1|VVVVxx |  1
> (8 rows)
> 
> That's not exactly my idea of "distinct" values of string4 ---
> but apparently whoever made up the regress test thought it was OK!
> 
> Can anyone defend this feature or provide a coherent definition
> of what it's supposed to be doing?  My urge to rip it out is
> growing stronger and stronger...
> 
> 			regards, tom lane
> 
> 


-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@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



view thread (10+ messages)  latest in thread

Message-ID: <199909231718.NAA19629@candle.pha.pa.us>
Permalink:  ../199909231718.NAA19629@candle.pha.pa.us/
Also on:    postgresql.org/message-id/199909231718.NAA19629@candle.pha.pa.us

 · 

reply

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: maillist@candle.pha.pa.us, tgl@sss.pgh.pa.us, hannu@trust.ee, hackers@postgreSQL.org
  Subject: Re: [SQL] Re: [HACKERS] SELECT DISTINCT question
  In-Reply-To: <199909231718.NAA19629@candle.pha.pa.us>
  References: <24413.931901508@sss.pgh.pa.us> <199909231718.NAA19629@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