From: | Sven Köhler <skoehler(at)upb(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruno Wolff III <bruno(at)wolff(dot)to>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: full featured alter table? |
Date: | 2003-06-14 18:17:38 |
Message-ID: | 3EEB66C2.1070502@upb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Perhaps, but pg_attribute is the natural place to keep the column
> ordering info.
i don't know what pg_attribute is, but sound to me like it is a good
sollution.
> 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.
it wouldn't matter much to me, if "select *" wouldn't be expanded in the
correct order, but it might worry other users.
the first thing to achieve is to define and offer a place where tools
can store the ordering information.
the second would be to make "select *" to use this information, although
this information should be well cached than if "select *" is expected
to be used often.
From | Date | Subject | |
---|---|---|---|
Next Message | weigelt | 2003-06-14 20:09:56 | Re: full featured alter table? |
Previous Message | Tom Lane | 2003-06-14 18:13:00 | Re: full featured alter table? |