Re: Reverse engineered Column definition incorrect

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Donald Fraser <demolish(at)cwgsy(dot)net>
Cc: "[pgADMIN]" <pgadmin-support(at)postgresql(dot)org>
Subject: Re: Reverse engineered Column definition incorrect
Date: 2003-10-02 18:17:21
Message-ID: 3F7C6BB1.1010900@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers pgadmin-support

Donald Fraser wrote:

> The reverse engineered code for column definitions if incorrect for
> DEFAULT values.
> I create table such as:
>
> REATE TABLE public.tbl_bkgndata
> (
> id int4 NOT NULL DEFAULT nextval('tbl_bkgndata_id_seq'::text),
> ) WITHOUT OIDS;
>
> Reverse engineered column definition is:
>
> ALTER TABLE public.tbl_bkgndata ADD COLUMN id int4;
> ALTER TABLE public.tbl_bkgndata ALTER COLUMN id SET STORAGE PLAIN;
> ALTER TABLE public.tbl_bkgndata ALTER COLUMN id SET NOT NULL;
> ALTER TABLE public.tbl_bkgndata ALTER COLUMN id DEFAULT
> nextval('tbl_bkgndata_id_seq'::text);
>
> Last row should read:
> ALTER TABLE public.tbl_bkgndata ALTER COLUMN id SET DEFAULT
> nextval('tbl_bkgndata_id_seq'::text);
>
> That is the key word SET is missing.

Fixed in cvs, thanks for reporting.

Regards,
Andreas

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message Godshall Michael 2003-10-02 21:17:29 Re: Bug in pgadmin III displaying/exporting dat
Previous Message Andreas Pflug 2003-10-02 18:15:24 wxWindows Upgrade

Browse pgadmin-support by date

  From Date Subject
Next Message Justin Honold 2003-10-02 20:12:02 not sure if you take non-list posts or not
Previous Message Hiroshi Saito 2003-10-02 16:51:51 Re: [pgadmin-support] Reverse engineered Column definition incorrect for DEFAULT