Re: [pgadmin-support] Reverse engineered Column definition incorrect for DEFAULT

From: "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp>
To: "Donald Fraser" <demolish(at)cwgsy(dot)net>
Cc: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>, <pgadmin-support(at)postgresql(dot)org>, <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: [pgadmin-support] Reverse engineered Column definition incorrect for DEFAULT
Date: 2003-10-02 16:51:51
Message-ID: 087201c38905$7aa45e20$1f324d80@w2k
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers pgadmin-support

Dear Donald.

Thank you very much.
It will be reflected soon.

Dave Apply it?

----- Original Message -----
From: Donald Fraser

> The reverse engineered code for column definitions if incorrect for DEFAULT values.
> I create table such as:

(snip)
> 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.

Attachment Content-Type Size
pgColumn_patch application/octet-stream 674 bytes

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message Hiroshi Saito 2003-10-02 17:33:26 Re: gcc ignoring defined macros?
Previous Message Dave Page 2003-10-02 16:08:28 Re: wxWindows Upgrade]

Browse pgadmin-support by date

  From Date Subject
Next Message Andreas Pflug 2003-10-02 18:17:21 Re: Reverse engineered Column definition incorrect
Previous Message Donald Fraser 2003-10-02 15:07:45 Reverse engineered Column definition incorrect for DEFAULT