From: Tom Lane <tgl@sss.pgh.pa.us>
To: dan@langille.org
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-sql@postgreSQL.org
Subject: Re: Uniqueness of rule, constraint, and trigger names
Date: Mon, 04 Mar 2002 15:47:52 -0500
Message-ID: <7683.1015274872@sss.pgh.pa.us> (raw)
In-Reply-To: <200203042043.g24Khek80028@lists.unixathome.org>
References: <200203042004.g24K4lk79699@lists.unixathome.org>
<200203042043.g24Khek80028@lists.unixathome.org>
"Dan Langille" <dan@langille.org> writes:
> It would be easily detected at load time. Then you direct the user to the
> tool mentioned above.
But if the user has already dumped and flushed his old installation,
he's still in need of a time machine.
Hmm, maybe what we need is a tool that can be applied during load.
Essentially, alter incoming constraint names as needed to make them
unique. We could have this enabled by a SET switch...
regards, tom lane
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: tgl@sss.pgh.pa.us, dan@langille.org, pgsql-hackers@postgreSQL.org
Subject: Re: Uniqueness of rule, constraint, and trigger names
In-Reply-To: <7683.1015274872@sss.pgh.pa.us>
* 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