From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Matthew <mboehm(at)voilaip(dot)com>, Bill Moran <wmoran(at)potentialtech(dot)com> |
Subject: | Re: Add Column BEFORE/AFTER another column |
Date: | 2007-08-24 22:14:30 |
Message-ID: | 200708241814.31411.xzilla@users.sourceforge.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Friday 24 August 2007 17:18, Matthew wrote:
> Hey Bill,
>
> > It does not.
>
> Bummer.
>
> > To get your columns in a specific order, specify the column names in
> > that order in your SELECT statement. The SQL standard doesn't provide
> > for any other way to guarantee column order, and neither does Postgres.
>
> Yes, I realize this and we do identify our columns during select
> statements, but when you look at a table using a tool like phpPGAdmin or
> pgAdmin3, the columns are displayed in some defined order. It's much
> easier to see your data/columns in some logical order (ie: all the cost
> columns next to each other).
>
FWIW (and it isnt much) we had the semblence of a patch and an actual plan for
implementing this, but no one got interested enough to finish it for 8.3.
Should you happen to know an ambituous C hacker, there is a good chance it
could be included in 8.4.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Cody Pisto | 2007-08-24 22:22:47 | Re: lc_collate issue |
Previous Message | Thomas Kellerer | 2007-08-24 22:14:23 | Re: PostgreSQL vs Firebird feature comparison finished |