Hitoshi Harada writes:
> 2010/10/15 Tom Lane :
>> 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 |
2010/10/15 Tom Lane :
> Hitoshi Harada 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 DISTIN
On Thu, Oct 14, 2010 at 10:37 AM, Hitoshi Harada wrote:
> I found PostgreSQL accepts UNION DISTINCT but documents don't mention it.
>
> http://www.postgresql.org/docs/9.0/static/sql-select.html#SQL-UNION
>
> select_statement UNION [ ALL ] select_statement
>
> UNION DISTINCT is nothing more than UN
Hitoshi Harada 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 d
I found PostgreSQL accepts UNION DISTINCT but documents don't mention it.
http://www.postgresql.org/docs/9.0/static/sql-select.html#SQL-UNION
select_statement UNION [ ALL ] select_statement
UNION DISTINCT is nothing more than UNION itself, but gram.y
definitely accept it and the SQL standard des
