Re: BUG #17408: Duplicate aliases silently fail - Mailing list pgsql-bugs

From John Naylor
Subject Re: BUG #17408: Duplicate aliases silently fail
Date
Msg-id CAFBsxsGV77vUbxHWJYE6RE9UZeLLYpZePk2Pu3Qw3a8QhSrQJg@mail.gmail.com
Whole thread Raw
In response to BUG #17408: Duplicate aliases silently fail  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Wed, Feb 16, 2022 at 5:46 PM PG Bug reporting form
<noreply@postgresql.org> wrote:

> Assigning aliases to columns works perfectly.
>
> eg. "SELECT name AS customer_name FROM customers"
>
> However you are able to assign duplicate aliases which does not cause a
> conflict
>
> eg. "SELECT name AS customer_name, surname AS customer_name FROM
> customers"
>
> The expectation here is that duplicate aliases would cause the query to fail
> due to duplicate column names in the result, however there is no error or
> warning.

FWIW, if the aliases are referenced higher up in a query, it does
result in error:

WITH dupe_cols AS (SELECT name AS customer_name, surname AS customer_name FROM
customers) SELECT customer_name FROM dupe_cols;
ERROR:  column reference "customer_name" is ambiguous
LINE 2: customers) select customer_name from dupe_cols;

-- 
John Naylor
EDB: http://www.enterprisedb.com



pgsql-bugs by date:

Previous
From: Kevin Potgieter
Date:
Subject: Re: BUG #17408: Duplicate aliases silently fail
Next
From: John Naylor
Date:
Subject: Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade