| From: | Bricklen Anderson <banderson(at)presinet(dot)com> |
|---|---|
| To: | emilu(at)encs(dot)concordia(dot)ca |
| Cc: | Pgsql-General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: RES: Add column and specify the column position in |
| Date: | 2006-05-18 16:02:40 |
| Message-ID: | 446C9AA0.5000506@presinet.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Emi Lu wrote:
>>
> No. It is not for select.
>
> I have tens of tables with very clean structure. For example, username,
> application_code, last_modified_by, etc in specific orders.
>
> Since the business model is changed, I have to add some columns to
> serveral tables.
>
> I prefer columns orders following my other tables.
>
>
>> In any case, there's extensive discussion about this in the -hackers
>> archives. IIRC, there is consensus that this would be nice to have but
>> no one has cared enough to actually make it happen. There are some
>> non-trivial issues since this would mean either completely re-writing
>> the table when you do an ALTER or you'd have to be able to divorce the
>> catalog representation of a table with the on-disk representation.
>> Though there are other advantages to doing the later, it's non-trivial.
>>
>>
> If it does not support, I will recreate my tables.
>
> Thanks.
>
Have you considered creating a view over the tables in question? You can
order the attributes in any fashion you like that way.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bob Pawley | 2006-05-18 16:02:51 | Re: Interface |
| Previous Message | Emi Lu | 2006-05-18 15:55:57 | Re: RES: Add column and specify the column position in |