From: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
---|---|
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-16 10:54:14 |
Message-ID: | Pine.LNX.4.21.0306161141430.3121-100000@ponder.fairway2k.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 16 Jun 2003, Jim C. Nasby wrote:
> On Sat, Jun 14, 2003 at 10:59:08AM -0500, Bruno Wolff III wrote:
> > 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.
>
> Actually, I was talking about the underlying order, because (at least
> the last time I asked about this), pgsql doesn't do any intelligent
> ordering under the covers. Because of that, I'd like to be able to order
> based on the optimal ordering I was given (fixed width before variable,
> then not null before null).
Ah, you see that's where the confusion comes from, everyone else is not on
about the physical ordering. I don't imagine core would consider an alter table
command to reorder columns in the tuple store.
--
Nigel J. Andrews
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-06-16 12:45:04 | Re: LC_COLLATE=es_MX in PgSQL 7.3.2 |
Previous Message | Richard Huxton | 2003-06-16 09:45:41 | Re: Odd error message |