Re: Reverse engineered Column definition incorrect

Hi Andreas,

Did you get it on both branches (& both changelogs)?

Regards, Dave.

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
> Sent: 02 October 2003 19:17
> To: Donald Fraser
> Cc: [pgADMIN]
> Subject: Re: [pgadmin-support] Reverse engineered Column
> definition incorrect
>
>
> 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
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: 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
>