Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (Postfix) with ESMTP id BCEBC47601B; Mon, 4 Mar 2002 17:13:16 -0500 (EST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 4646CD5FD; Mon, 4 Mar 2002 14:13:18 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 37C0A5BFC; Mon, 4 Mar 2002 14:13:18 -0800 (PST) Date: Mon, 4 Mar 2002 14:13:18 -0800 (PST) From: Stephan Szabo To: Tom Lane Cc: , Subject: Re: Uniqueness of rule, constraint, and trigger names In-Reply-To: <7131.1015269848@sss.pgh.pa.us> Message-ID: <20020304140956.F80841-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200203/47 X-Sequence-Number: 6929 On Mon, 4 Mar 2002, 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 Another question would be what to do with inherited constraints that conflict in multiple inheritance cases. It'd probably be safe to rename those on the child table to be unique, but then drop constraint may become more involved (and the error messages no longer use the name given by the user for either constraint).