At 10:32 PM 06/14/2003 +0200, weigelt@metux.de wrote:
>On Sat, Jun 14, 2003 at 10:18:30PM +0200, Sven K?hler wrote:
>
><snip>
>> what are you talking about? it is not _my_ frontend!
>> we're talking "frontends" about 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)
I tend to agree that column ordering does not belong in that database.
Simply because I find it hard to believe that yuo would only and always
want "SELECT *" to come across to the client in a specific order. Context
indicates what the column order needs to be.
One other wrinkle is what to do wth "SELECT * from tablea, tableb" Do you
use all of tablea and then all of tableb? Or interleave with (first from
tablea, first from tableb, second from tablea, second from tableb...)
Besides I usually load a record in a dictionary structure in my client
language (python or smalltalk) which means a) the order is based on the
hash ordering of the dictionary structure anyway and b) I'm doing things by
name, not position.
Take care,
Jay