From: | Miernik <miernik(at)ctnet(dot)pl> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: ALTER TABLE DROP COLUMN |
Date: | 2003-07-30 17:59:07 |
Message-ID: | bg911b$rjj$1@main.gmane.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
In article <27820(dot)1046900280(at)sss(dot)pgh(dot)pa(dot)us>, Tom Lane wrote:
>> The result is that column x is now a replaced by a column called
>> "........pg.dropped.4........."
>> exists in its place, and now my odbc connections won't touch the table.
>
> You need a newer version of the ODBC driver (one that understands about
> dropped columns).
I see the same thing when I access my table with phppgadmin 2.4.1-2
from Debian, Isn't there any way to just get rid of the dropped column
remains completely? Just as if the column never existed?
Something else then dumping the database, editing the dump file with a
text editor to delete the unnessesary column and restoring the
database.
--
Miernik
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Vit | 2003-07-30 20:01:38 | Re: designing tables - sidetrack into arrays |
Previous Message | Tom Lane | 2003-07-30 15:13:32 | Re: designing tables for blobs - what are the guidelines? |