>>what are you talking about? it is not _my_ frontend!
>>we're talking about "frontends" like pgAdmin, phpPgAdmin etc.
>
> yes. why couldnt they simply use an extra table for this - just
> like pgaccess does for storing its config ?
> user-side column odering is frontend stuff.
> it dont like the idea that SELECT * doesnt use the physical order
> (from pg_attribute - which you also can see w/ \d in the pgsql frontend)
so why don't you like it to use the user-defined order? do _you_ use
"select *" ?
BTW: if you change the user-defined order, it will match the physical
order, so you it's something you don't have to care about.
If the postgresql-team decides, that the column-order is not to be
stored in the sys-tables, that it woul be the last step to store it in
some other tables, but that is the worst step, as each tool will surely
have it own tables etc. if it ones to support column ordering.
if you think that column-ordering is just luxury, than i might remind
you, table-names and column-names are just luxury too ;-)
