From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kyle <kyle@actarg.com>
Cc: pgsql-sql@postgresql.org, Peter Eisentraut <peter_e@gmx.net>
Subject: Re: Getting FK relationships from information_schema
Date: Wed, 09 Jun 2004 01:04:47 -0400
Message-ID: <16089.1086757487@sss.pgh.pa.us> (raw)
In-Reply-To: <40C5D790.6090407@actarg.com>
References: <40C500D8.9060009@actarg.com>
<26677.1086673982@sss.pgh.pa.us>
<40C5D790.6090407@actarg.com>
Kyle <kyle@actarg.com> writes:
> I think this is only an issue when the user relies on postgres to choose
> a constraint name automatically. Seems like a reasonable approach would
> be to have postgres choose a name for the constraint that happens to be
> unique in the schema (like tablename_fkey_$1).
We have discussed changing the default names of FK constraints before.
I have no problem with doing something like the above --- any objection
out there?
(Of course, this is only a long-term fix for your original problem,
as it'll take a good long while for any such naming change to propagate
to Joe's-Corner-Bar's database.)
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, kyle@actarg.com, peter_e@gmx.net
Subject: Re: Getting FK relationships from information_schema
In-Reply-To: <16089.1086757487@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