From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Jan Wieck <JanWieck@Yahoo.com>
Cc: Markus Bertheau <twanger@bluetwanger.de>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: olly@lfix.co.uk, pgsql-sql@postgresql.org, Bruce Momjian <pgman@candle.pha.pa.us>
Subject: Re: multi column foreign key for implicitly unique columns
Date: Wed, 18 Aug 2004 07:38:44 -0700 (PDT)
Message-ID: <20040818073152.W1646@megazone.bigpanda.com> (raw)
In-Reply-To: <41236277.5060903@Yahoo.com>
References: <1092734724.2627.4.camel@dicaprio.akademie1.de>
<1092735576.28365.48.camel@linda>
<1092736197.2627.12.camel@dicaprio.akademie1.de>
<200408171945.15663.josh@agliodbs.com>
<41235A90.1080300@Yahoo.com>
<1092836961.2630.3.camel@dicaprio.akademie1.de>
<41236277.5060903@Yahoo.com>
On Wed, 18 Aug 2004, Jan Wieck wrote:
> On 8/18/2004 9:49 AM, Markus Bertheau wrote:
>
> > РСÑд, 18.08.2004, в 15:33, Jan Wieck пиÑеÑ:
> >
> >> Meaning that not enforcing the uniqueness of those columns isn't an
> >> option.
> >
> > The thing is that the columns _are_ unique, there's just no unique
> > constraint on them. They are unique because there's a unique constraint
> > on a subset of these columns. So no additional uniqueness enforcing
> > needed.
> >
>
> Yes, you are right, a superset of columns of a unique constraint is
> allways unique as well.
True, but the spec explicitly asks for the columns to be the members of a
unique constraint, not that the columns be provably unique. See the other
portion of the thread related to dropping constraints for other spec
extensions doing this implies. I think the actual specific change to make
it look for the subset should be trivial, but we'd really need to work
out those dependency issues at the very least and I'm afraid there are
more such little corners.
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@megazone.bigpanda.com, JanWieck@Yahoo.com, twanger@bluetwanger.de, josh@agliodbs.com, pgman@candle.pha.pa.us
Subject: Re: multi column foreign key for implicitly unique columns
In-Reply-To: <20040818073152.W1646@megazone.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