Re: bigserial problem - Mailing list pgadmin-support

From Andreas Pflug
Subject Re: bigserial problem
Date
Msg-id 4342BCD2.50602@pse-consulting.de
Whole thread Raw
In response to bigserial problem  (rich.morrison@atxinc.com)
Responses Re: bigserial problem  (rich.morrison@atxinc.com)
List pgadmin-support
rich.morrison@atxinc.com wrote:
> 
> pgAdmin reports a SQL error when attempting to add a bigserial column to 
> an existing table.

I checked this, it works.

> 
> Adding the column produces this SQL statement:
> 
> CREATE SEQUENCE public.tblenglish_in_trnas_id_seq;
> ALTER TABLE tblenglish_in
>    ADD COLUMN trnas_id int8;
> ALTER TABLE tblenglish_in
>    ALTER COLUMN trnas_id SET DEFAULT 
> nextval('public.tblenglish_in_trnas_id_seq'::text);
> INSERT INTO pg_depend(classid, objid, objsubid, refclassid, refobjid, 
> refobjsubid, deptype)
> SELECT cl.oid, seq.oid, 0, cl.oid, 17154::oid, attnum, 'i'
>   FROM pg_class cl, pg_attribute, pg_class seq
>   JOIN pg_namespace sn ON sn.OID=seq.relnamespace
>  WHERE cl.relname='pg_class'
>   AND seq.rel

Not quite. The resulting sql query can be taken from the SQL page of the 
dialog. What you present here is probably what's logged in pgadmin.log, 
which might get truncated to 1k (AFAIR) for technical reasons.

Regards,
Andresa


pgadmin-support by date:

Previous
From: Max Giesbert
Date:
Subject: rpmbuild not working with pgadmin v 1.2.2 src rpm under fedora core 4
Next
From: rich.morrison@atxinc.com
Date:
Subject: Re: bigserial problem