Received: from lists.unixathome.org (lists.unixathome.org [210.48.103.158]) by postgresql.org (Postfix) with ESMTP id 4D6CE476AE4; Mon, 4 Mar 2002 15:05:03 -0500 (EST) Received: from wocker (lists.unixathome.org [210.48.103.158]) by lists.unixathome.org (8.11.6/8.11.6) with ESMTP id g24K4lk79699; Tue, 5 Mar 2002 09:04:47 +1300 (NZDT) (envelope-from dan@lists.unixathome.org) Message-Id: <200203042004.g24K4lk79699@lists.unixathome.org> From: "Dan Langille" Organization: DVL Software Limited To: Tom Lane Date: Mon, 4 Mar 2002 15:04:45 -0500 MIME-Version: 1.0 Subject: Re: Uniqueness of rule, constraint, and trigger names Reply-To: dan@langille.org Cc: pgsql-hackers@postgreSQL.org, pgsql-sql@postgreSQL.org In-reply-to: <7131.1015269848@sss.pgh.pa.us> X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Archive-Number: 200203/39 X-Sequence-Number: 6921 On 4 Mar 2002 at 14:24, Tom Lane wrote: > For constraints, we'd need to change the code to be more careful to > generate unique names for unnamed constraints. That doesn't seem > difficult, but I'm a little worried about the possibility of errors > in loading schemas from existing databases, where there might be > non-unique constraint names. Create a tool to generate unique constraint names during a dump. Sounds like a pg_dump[all] switch to me. > Perhaps it'd be safer to maintain the > current behavior (no uniqueness required for constraint names). I would rather see a simple and unambigous way to maintain a single constraint. Perhaps a "unique/not-unique" knob is appropriate. -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ - practical examples