From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: UNION DISTINCT in doc |
Date: | 2010-10-15 19:51:02 |
Message-ID: | 10628.1287172262@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> writes:
> 2010/10/15 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> I think it'd be hard to describe without confusing people, because
>> while DISTINCT is a noise word there, it's definitely not a noise
>> word after SELECT.
> I thought adding DISTINCT next to ALL is enough like
> select_statement UNION [ ALL | DISTINCT ] select_statement
> and say "UNION DISTINCT is identical to UNION only" or something. That
> sounds not so confusing with DISTINCT clause description.
I looked at this more closely and decided that we could probably avoid
confusion if the description of the "DISTINCT clause" was careful to say
SELECT DISTINCT and SELECT ALL, rather than just DISTINCT/ALL.
Committed that way.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2010-10-15 20:03:25 | Re: host name support in pg_hba.conf |
Previous Message | Josh Kupershmidt | 2010-10-15 19:49:48 | Re: [GENERAL] column-level update privs + lock table |