Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (Postfix) with ESMTP id 3BA5C475998; Mon, 4 Mar 2002 17:51:18 -0500 (EST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 3AAC9D60A; Mon, 4 Mar 2002 14:51:16 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 302415BFC; Mon, 4 Mar 2002 14:51:16 -0800 (PST) Date: Mon, 4 Mar 2002 14:51:16 -0800 (PST) From: Stephan Szabo To: Tom Lane Cc: , Subject: Re: Uniqueness of rule, constraint, and trigger names In-Reply-To: <8491.1015280312@sss.pgh.pa.us> Message-ID: <20020304145040.R81357-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200203/49 X-Sequence-Number: 6931 On Mon, 4 Mar 2002, Tom Lane wrote: > Stephan Szabo writes: > > 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, > > I'd just raise an error, I think, unless perhaps the constraints are > identical (for some definition of identical). We don't allow > conflicting column definitions to be inherited, so why constraints? Good point. That's probably better than autorenaming them.