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-14 15:00:14 |
Message-ID: | 18507.1287068414@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:
> UNION DISTINCT is nothing more than UNION itself, but gram.y
> definitely accept it and the SQL standard describes it as well. Should
> we add DISTINCT to docs?
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. And the way that the reference pages are laid
out, it's hard to connect different descriptions of the same
keyword to different usages. If you can think of a non-forced
way of describing this, fine. But I don't have a problem with
leaving it as an undocumented standards-compliance nit.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-10-14 15:04:05 | Re: SQL command to edit postgresql.conf, with comments |
Previous Message | David Newall | 2010-10-14 14:54:04 | Re: rollback to savepoint leads to transaction already in progress |