From: "Greg Patnude" <gpatnude@hotmail.com>
Subject: Re: nextval problem
Date: Mon, 16 Feb 2004 09:51:46 -0800
Organization: Hub.Org Networking Services
Lines: 45
Message-ID: <c0r018$2psh$1@news.hub.org>
References: <h7WWb.13725$2Z2.1853@amsnews05.chello.com>
To: pgsql-sql@postgresql.org

New feature for posgreSQL 7.3 & later -- sequences are automatically dropped
when the owning table is dropped -- you need to recreate the sequence....

The easiest way is in your CREATE TABLE tblName (

    id serial PRIMARY KEY,
    blah...,
    blah...,

) WITH OIDS;

-- 
Greg Patnude / The Digital Demention
2916 East Upper Hayden Lake Road
Hayden Lake, ID 83835
(208) 762-0762

"Ivo Anon" <ivoa72@hotmail.com> wrote in message
news:h7WWb.13725$2Z2.1853@amsnews05.chello.com...
> I'm new to postgresql and I'm having problems with the 'nextval' function
> (or whatever it is called in postgresql).
>
> I created a table (called ADDRESS) using 'pgadmin' which has a serial
field
> (called addressid). When I tried the sql statement:
>
>         select nextval('public."ADDRESS_addressid_seq"')
>
> everything seemed to be working fine.
>
> I then used the create table statement (displayed in pgadmin when the
table
> 'ADDRESS' is selected) to create the same table (of course after first
> dropping 'ADDRESS'). When I try the same select-statement I suddenly got
an
> error message saying:
>
>         ERROR:  Relation "public"."ADDRESS_addressid_seq" does not exist
>
> Can anybody help me with this problem?
>
>