From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
Subject: | Re: Simple Column reordering |
Date: | 2007-02-23 10:25:07 |
Message-ID: | 200702231125.09127.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Am Freitag, 23. Februar 2007 09:08 schrieb Simon Riggs:
> If this is standards-breaking as you say, I would withdraw immediately.
> I checked the SQL standard and could not see how this would do so. The
> standard states SELECT * would return columns in order; it doesn't say
> what that order should be,
b) Otherwise, the <select list> “*” is equivalent to a <value expression>
sequence in which each <value expression> is a column reference that
references a column of T and each column of T is referenced exactly once. The
columns are referenced in the ascending sequence of their ordinal position
within T.
> nor does CREATE TABLE enforce the ordering to
> be the same as it has specified, AFAICS.
b) The column descriptors of every column of T, according to the Syntax Rules
and General Rules of Subclause 11.4, “<column definition>”, applied to the
<column definition>s contained in TEL, in the order in which they were
specified.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
From | Date | Subject | |
---|---|---|---|
Next Message | Vishal Arora | 2007-02-23 10:58:17 | Data Restore from WAL |
Previous Message | Peter Eisentraut | 2007-02-23 10:15:22 | Re: tsearch in core patch, for inclusion |