From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
Cc: | Sven Köhler <skoehler(at)upb(dot)de>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: full featured alter table? |
Date: | 2003-06-14 18:13:00 |
Message-ID: | 8648.1055614380@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Bruno Wolff III <bruno(at)wolff(dot)to> writes:
> Sven Khler <skoehler(at)upb(dot)de> wrote:
>> let's express it another way: we want to define the order of the columns
>> when they are shown in tools like phpPgAdmin or PgAdminII.
> That is something that those tools should do then. It isn't really a
> postgres issue as it already provides ways for the tools to get
> information about columns of a table.
Perhaps, but pg_attribute is the natural place to keep the column
ordering info.
ISTM we talked months ago about adding an "attlognum" column to
pg_attribute, which would be separate from "attnum" (the physical column
position) and would be used by the backend only to determine the order
of SELECT * expansion. Admin tools could use this to determine column
display order too. It didn't get done, but it still seems like a
reasonable idea to me.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sven Köhler | 2003-06-14 18:17:38 | Re: full featured alter table? |
Previous Message | Sven Köhler | 2003-06-14 17:59:19 | Re: full featured alter table? |