From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: full featured alter table? |
Date: | 2003-06-14 15:59:08 |
Message-ID: | 20030614155908.GC29302@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Jun 14, 2003 at 10:31:02 -0500,
"Jim C. Nasby" <jim(at)nasby(dot)net> wrote:
>
> The one thing we don't have that I think would be useful is a way to
> re-order the columns in a table. Maybe it's just me, but I tend to want
> column to appear in a specific order, and the only way you can
> accomplish this today is by re-creating the entire table.
You can specify the order that columns are output now. The real underlying
order should really be up to postgres to decide based on what is most
efficient.
If you were thinking about the order you get when you use * as a shorthand
for all of the columns, perhaps there could be some way to change that
without actually changing the order of the columns in the table.
I doubt it would be a good idea to do that though. It is already a bad
idea to use * in applications in case something does change the order
or number of columns. * is mostly going to be used in adhoc queries
where you care about saving some typing. It may not be worth adding
a feature like that for the limited amount of use it would get.
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Clift | 2003-06-14 16:21:52 | Re: [HACKERS] SAP and MySQL ... [and Benchmark] |
Previous Message | Tino Wildenhain | 2003-06-14 15:55:44 | Re: Insert NULL for '' |