Hi Andreas,
This is a little worrying - I just tried it here and when trying to set
a comment on a table, what it actually executed was:
ALTER TABLE fig.test ADD COLUMN fooCol fig.foo_domain;
ALTER TABLE fig.test ADD COLUMN myFatCol int4[];
ALTER TABLE fig.test DROP COLUMN "fooCol";
ALTER TABLE fig.test DROP COLUMN "myFatCol";
Which appeared to fail without error. Also, selecting a column and
clicking Change does nothing.
The table defn was:
CREATE TABLE fig.test
( foocol fig.foo_domain, myfatcol int4[]
) WITH OIDS;
Regards, Dave.
> -----Original Message-----
> From: Terence Kearns [mailto:terencek@isd.canberra.edu.au]
> Sent: 16 July 2003 03:33
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] pgAdmin3: adding comments to
> existing tables
>
>
> because the interface attempts to "re-submit all" of the
> properties of
> the existing table for alteration, if you want to change any one
> property of a table, you need to re-apply all properties.
> This has the
> undesired side-effect of failing *any* modification to a
> table if any of
> the other *existing* properties fail to qualify for
> re-applying through
> ALTERing.
>
> For instance, I have a table containing a column with a default value.
>
> When I try to use pgAdmin3 to add(modify) a(the) comment to
> that table,
> the operation fails with the message.
>
> ERROR: Adding columns with defaults is not implementd...
>
> This is silly bacause my intent was not to add a column. I think this
> may be a user-interface design limitation.
>
> --
> Terence Kearns ~ ph: +61 2 6201 5516
> IT Database/Applications Developer
> Enterprise Information Systems
> Client Services Division
> University of Canberra
> www.canberra.edu.au
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>