Re: alter table add column - specify where the column will go? - Mailing list pgsql-general

From Daniel Verite
Subject Re: alter table add column - specify where the column will go?
Date
Msg-id eceaf1e4-e485-4cb2-b587-d1dfacd7ab93@mm
Whole thread Raw
In response to Re: alter table add column - specify where the column will go?  (Fredric Fredricson <Fredric.Fredricson@bonetmail.com>)
List pgsql-general
    Fredric Fredricson wrote:

> But if you change the column names in the second SELECT in the UNION this is
> ignored:
> # SELECT c1,c2 FROM (SELECT 1 AS c1, 2 AS c2 UNION SELECT 2 AS c3, 1 AS c4)
> AS x;
>  c1 | c2
> ----+----
>   1 |  2
>   2 |  1
> Apparently, in a UNION the column names are derived from the first statement
> only.

The example upthread demonstrates that in certain contexts, column positions
are relevant whereas column names are not. The modified query you show here
doesn't lead to any different conclusion.

The allegation that row.* doesn't come with a deterministic column order
remains pretty much unsubstantiated at this point.

Best regards,
--
Daniel
PostgreSQL-powered mail user agent and storage: http://www.manitou-mail.org

pgsql-general by date:

Previous
From: Fredric Fredricson
Date:
Subject: Re: alter table add column - specify where the column will go?
Next
From: akp geek
Date:
Subject: Postgres 9 and postgis1.5.2