Re: Reverse engineered Column definition incorrect - Mailing list pgadmin-support

From Andreas Pflug
Subject Re: Reverse engineered Column definition incorrect
Date
Msg-id 3F7C6BB1.1010900@pse-consulting.de
Whole thread Raw
In response to Reverse engineered Column definition incorrect for DEFAULT  ("Donald Fraser" <demolish@cwgsy.net>)
List 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




pgadmin-support by date:

Previous
From: "Hiroshi Saito"
Date:
Subject: Re: Reverse engineered Column definition incorrect for DEFAULT
Next
From: Godshall Michael
Date:
Subject: Bug in pgadmin III displaying/exporting data from query window(tr uncating)