Re: sequences not renamed with tables - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: sequences not renamed with tables
Date
Msg-id 2e7bc154d174560c2614258f65b00e6e@biglumber.com
Whole thread Raw
In response to sequences not renamed with tables  (CSN <cool_screen_name90001@yahoo.com>)
List pgsql-general
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> I renamed a couple tables, and the names of their
> corresponding sequences remained the same. This causes
> a problem because when importing - the create table
> statements create sequences with different names, then
> the setval() statements use the old names. Any way to
> automatically avoid this "gotcha"?

Don't rely on the create table to make the sequences for
you: declare them yourself. Instead of this:

CREATE TABLE foobar (
  id  SERIAL
);

Try this:

CREATE SEQUENCE barbell_seq;

CREATE TABLE foobar (
  id INTEGER NOT NULL DEFAULT nextval('barbell_seq')
);

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200312172134

-----BEGIN PGP SIGNATURE-----

iD8DBQE/4RJjvJuQZxSWSsgRAgEdAJ9y4eDaQENuRWVRETJdLu/vKO5PggCeKLjs
dkPyceUBRMkTbvcqMBAgLr4=
=5b5j
-----END PGP SIGNATURE-----



pgsql-general by date:

Previous
From: "Alice Bag"
Date:
Subject: Re: Firebird and PostgreSQL at the DB Corral.
Next
From: Paul Ganainm
Date:
Subject: Re: Firebird and PostgreSQL at the DB Corral.