| From: | Pantelis Theodosiou <ypercube(at)gmail(dot)com> |
|---|---|
| To: | porturpotgieter(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17408: Duplicate aliases silently fail |
| Date: | 2022-02-16 12:02:12 |
| Message-ID: | CAE3TBxzVw=VFVav=zUo5LyeE+oUiOktOfDbRfDxcA4_6QjWS9g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Feb 16, 2022 at 10:46 AM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 17408
> Logged by: Kevin Potgieter
> Email address: porturpotgieter(at)gmail(dot)com
> PostgreSQL version: 13.6
> Operating system: Not related
> Description:
>
> Hi,
>
> 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.
This may look weird but the SQL standard allows it. Postgres is only
following what the standard dictates.
Best regards,
Pantelis Theodosiou
>
> Regards
> Kevin
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Potgieter | 2022-02-16 12:05:13 | Re: BUG #17408: Duplicate aliases silently fail |
| Previous Message | Sergei Kornilov | 2022-02-16 11:03:41 | Re:BUG #17407: trim trims more than expected |