From: | Jean-Luc Lachance <jllachan(at)nsd(dot)ca> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruno Wolff III <bruno(at)wolff(dot)to>, "Sven =?iso-8859-1?Q?K=F6hler?=" <skoehler(at)upb(dot)de>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: full featured alter table? |
Date: | 2003-06-16 19:25:33 |
Message-ID: | 3EEE19AD.F592E020@nsd.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Really?
What if two PgAdmin sessions want two different order?
Presentation order should be done at the application level.
JLL
Tom Lane wrote:
>
> Bruno Wolff III <bruno(at)wolff(dot)to> writes:
> > Sven Köhler <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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
From | Date | Subject | |
---|---|---|---|
Next Message | Tino Wildenhain | 2003-06-16 19:26:12 | Re: RE : full featured alter table? |
Previous Message | scott.marlowe | 2003-06-16 19:00:14 | Re: Postgres performance comments from a MySQL user |