From: | Sim Zacks <sim(at)compulab(dot)co(dot)il> |
---|---|
To: | Chris <chris(dot)velevitch(at)gmail(dot)com> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: [1.4rc1] Can't change column type |
Date: | 2005-11-06 08:54:51 |
Message-ID: | 349864419.20051106105451@compulab.co.il |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
I get a lot of benefit out of PGAdmin without that functionality.
It's actually a database limitation, not a PGAdmin limitation.
However, if your main database activity is changing the data type of a
column in ways that are disallowed by PostGreSQL, then you are
correct. PGAdmin is pointless.
Sim Zacks
CIO
CompuLab
04-829-0145 - Office
04-832-5251 - Fax
________________________________________________________________________________
Joost Kraaijeveld <J.Kraaijeveld <at> Askesis.nl> writes:
> Does this work (replace the names according to your schema)?
>
> BEGIN;
> ALTER TABLE table_name ADD COLUMN new_column varchar(64)?;
> UPDATE table_name SET new_column = column;
> ALTER TABLE customer RENAME column TO old_column;
> ALTER TABLE customer RENAME new_column TO columns;
> COMMIT;
In the end, I did this plu I dropped the old column, but what's the point of
having a tool like pgAdmin if common place everyday activities like this can't
be done?
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Velevitch | 2005-11-06 09:11:50 | Re: [1.4rc1] Can't change column type |
Previous Message | Joost Kraaijeveld | 2005-11-06 08:52:42 | Re: [1.4rc1] Can't change column type |