| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Ashish Karalkar" <ashish(dot)karalkar(at)info-spectrum(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Column Ordering |
| Date: | 2007-09-10 17:41:33 |
| Message-ID: | dcc563d10709101041u654a1e50k5c0add702aaaa260@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 9/10/07, Ashish Karalkar <ashish(dot)karalkar(at)info-spectrum(dot)com> wrote:
>
>
>
> Hello All,
>
> I am having a table with 5 columns.
> I want to add another column by altering the table at 2nd position
> constraint is that I can not drop and recreate the table as column ordering
> is of importance.
That doesn't make sense. dropping and recreating the table isn't
really constrained by column ordering. Now, if you've got FK
constraints, other triggers, rules, etc... then I can see those being
an issue.
> Is there anyway to do so.
Not without dropping and recreating the table OR creating an updatable
view on top of it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Darek Czarkowski | 2007-09-10 18:13:36 | Re: Postgresql 7.3 on Red Hat Enterprise 5 (Problem with SEMMNI, SEMMNS) |
| Previous Message | brian | 2007-09-10 17:09:53 | Re: Column ordering |