From: | Mike Mascari <mascarm(at)mascari(dot)com> |
---|---|
To: | Ernest E Vogelsinger <ernest(at)vogelsinger(dot)at> |
Cc: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>, Sven Köhler <skoehler(at)upb(dot)de>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: full featured alter table? |
Date: | 2003-06-15 11:49:39 |
Message-ID: | 3EEC5D53.9070905@mascari.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ernest E Vogelsinger wrote:
> At 12:33 15.06.2003, Nigel J. Andrews said:
> --------------------[snip]--------------------
>
>>Well, on the basis that column ordering is presentation issue it does
>>belong in
>>the frontend. However, as Tom pointed out this discussion was had a few
>>months. I can't remember the outcome but apparently a suggestion was to have a
>>column in pg_attribute giving the presentational order.
>
> --------------------[snip]--------------------
>
> Holdit.
>
> This whole thread eveolves to something asking a car designer to design a
> car in a way a particular color would come best...
>
> I believe column ordering should be decided by the database itself, to
> maximize output/throughput or otherwise beneficially influent performance
> and/or disk usage. If you want a specific column sequence, put it into the
> SELECT statement. '*' just means "gimme all of them", not in a particular
> order.
The proposal does beg the question:
Why would a default tuple-attribute order be stored in the database
but not relation-tuple order?
Mike Mascari
mascarm(at)mascari(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert C. Paulsen Jr. | 2003-06-15 12:22:11 | Re: crypt vs password in pg_hba.conf |
Previous Message | Ernest E Vogelsinger | 2003-06-15 11:04:23 | Re: full featured alter table? |