Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 1B3D047598E; Mon, 4 Mar 2002 18:05:07 -0500 (EST) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.2) with HTTP id 816616; Mon, 04 Mar 2002 15:05:07 -0800 From: "Josh Berkus" Subject: Re: Uniqueness of rule, constraint, and trigger names To: Tom Lane , pgsql-hackers@postgreSQL.org, pgsql-sql@postgreSQL.org X-Mailer: CommuniGate Pro Web Mailer v.3.5.2 Date: Mon, 04 Mar 2002 15:05:07 -0800 Message-ID: In-Reply-To: <7131.1015269848@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200203/51 X-Sequence-Number: 6933 Tom, > Currently we have a rather confusing mismash of behaviors for the > names > of rules, constraints, and triggers. I'd like to unify the rules > so that these objects all have the same naming behavior; and the only > behavior that makes sense to me now is that of triggers. I agree. Regarding prioritization: As a heavy user of constraints and triggers, on two commercial projects, I have yet to have constraint names overlap. What's more of a problem for me is those pesky constraints. -Josh Berkus