| From: | Chris Bitmead <chris(at)bitmead(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] DISTINCT ON: speak now or forever hold your peace |
| Date: | 2000-01-25 06:07:03 |
| Message-ID: | 388D3D87.C1BCE49B@bitmead.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
Philip Warner wrote:
> >In fact, this is a KEY notion behind RDBMS systems...queries return an
> >unordered set, pure and simple, unless you supply an "order" clause
> >(though "group by" appears to be implemented by ordering in various
> >RDBMS systems, that's an efficiency hack not a given AFAIK).
On second thoughts, maybe I agree DISTINCT ON should be dumped. In my
example, if I wanted the youngest people with a given name sorted oldest
first things would be confusing. It's an inconsistant command, I can see
that now.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-01-25 06:12:46 | Re: [HACKERS] DISTINCT ON: speak now or forever hold your peace |
| Previous Message | Michael Robinson | 2000-01-25 06:05:36 | Re: [HACKERS] fatal copy in/out error (6.5.3) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-01-25 06:12:46 | Re: [HACKERS] DISTINCT ON: speak now or forever hold your peace |
| Previous Message | Philip Warner | 2000-01-25 06:00:26 | Re: [HACKERS] DISTINCT ON: speak now or forever hold your peace |