Re: [PATCHES] Non-colliding auto generated names

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Non-colliding auto generated names
Date: 2003-02-21 07:23:50
Message-ID: 0a3501c2d97a$2e6c9260$6500a8c0@fhp.internal
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

OK,

I have discovered a problem with my auto-naming patch. It's do to with
dumping serial columns with pg_dump, eg:

--
-- TOC entry 2 (OID 1004551)
-- Name: users_users; Type: TABLE; Schema: public; Owner: chriskl
--

CREATE TABLE users_users (
userid serial NOT NULL,
firstname character varying(255) NOT NULL,
lastname character varying(255) NOT NULL,
email character varying(255) NOT NULL
);

-- DATA DUMPED HERE

--
-- TOC entry 4 (OID 1004305)
-- Name: users_users_userid_seq; Type: SEQUENCE SET; Schema: public; Owner:
chriskl
--

SELECT pg_catalog.setval ('users_users_userid_seq', 126, true);

How do we fix this problem?? Perhaps instead of a hard-coded sequence
string, we can sub-SELECT for it...?

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2003-02-21 08:10:00 Re: request for sql3 compliance for the update command
Previous Message Greg Stark 2003-02-21 06:56:12 Re: request for sql3 compliance for the update command

Browse pgsql-patches by date

  From Date Subject
Next Message Gavin Sherry 2003-02-21 10:45:26 Minor doc patch: create function
Previous Message Neil Conway 2003-02-21 07:18:04 Re: psql patch