From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-sql@postgreSQL.org
Subject: Re: Uniqueness of rule, constraint, and trigger names
Date: Mon, 4 Mar 2002 14:51:16 -0800 (PST)
Message-ID: <20020304145040.R81357-100000@megazone23.bigpanda.com> (raw)
In-Reply-To: <8491.1015280312@sss.pgh.pa.us>
On Mon, 4 Mar 2002, Tom Lane wrote:
> Stephan Szabo <sszabo@megazone23.bigpanda.com> 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.
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: sszabo@megazone23.bigpanda.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org
Subject: Re: Uniqueness of rule, constraint, and trigger names
In-Reply-To: <20020304145040.R81357-100000@megazone23.bigpanda.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