From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@postgreSQL.org
To: pgsql-sql@postgreSQL.org
Subject: Re: Uniqueness of rule, constraint, and trigger names
Date: Mon, 04 Mar 2002 15:05:07 -0800
Message-ID: <web-816616@davinci.ethosmedia.com> (raw)
In-Reply-To: <7131.1015269848@sss.pgh.pa.us>
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 <unnamed>
constraints.
-Josh Berkus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org
Subject: Re: Uniqueness of rule, constraint, and trigger names
In-Reply-To: <web-816616@davinci.ethosmedia.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox