Thanks :-)
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 03 October 2003 11:15
> To: Dave Page
> Cc: [pgADMIN]
> Subject: Re: [pgadmin-support] Reverse engineered Column
> definition incorrect
>
>
> Dave Page wrote:
>
Dave Page wrote:
Hi Andreas,
Did you get it on both branches (& both changelogs)?
Ahem...
done now.
Regards,
Andreas
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Hi Andreas,
Did you get it on both branches (& both changelogs)?
Regards, Dave.
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 02 October 2003 19:17
> To: Donald Fraser
> Cc: [pgADMIN]
> Subject: Re: [pgadmin-support] Rev
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
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 i
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_bk
