Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 334DF47615F; Mon, 4 Mar 2002 17:18:41 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g24MIXS08494; Mon, 4 Mar 2002 17:18:33 -0500 (EST) To: Stephan Szabo Cc: pgsql-hackers@postgreSQL.org, pgsql-sql@postgreSQL.org Subject: Re: Uniqueness of rule, constraint, and trigger names In-reply-to: <20020304140956.F80841-100000@megazone23.bigpanda.com> References: <20020304140956.F80841-100000@megazone23.bigpanda.com> Comments: In-reply-to Stephan Szabo message dated "Mon, 04 Mar 2002 14:13:18 -0800" Date: Mon, 04 Mar 2002 17:18:32 -0500 Message-ID: <8491.1015280312@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200203/48 X-Sequence-Number: 6930 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? regards, tom lane