From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
Cc: | <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: FW: pgAdmin3: adding comments to existing tables |
Date: | 2003-07-16 11:19:23 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B844B300@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
> Sent: 16 July 2003 11:47
> To: Dave Page
> Cc: pgadmin-support(at)postgresql(dot)org
> Subject: Re: FW: [pgadmin-support] pgAdmin3: adding comments
> to existing tables
>
>
> Dave Page wrote:
>
> >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";
> >
> OK, took quite a while until I understood what's going on.
> qtIdent was
> missing on the column name, and fooCol is not the same as "fooCol" so
> the mechanism to determine if a column definition is already present
> didn't hit.
Looks OK now, though the definition pane needs a refresh to see the
changes.
> >Also, selecting a column and clicking Change does nothing.
> >
> Not implemented...
OK.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2003-07-16 12:08:20 | pgAdmin III Screenshots |
Previous Message | Andreas Pflug | 2003-07-16 10:47:11 | Re: FW: pgAdmin3: adding comments to existing tables |