From: Josh Berkus <josh@agliodbs.com>
To: sqllist <pgsql-sql@postgresql.org>
Subject: Is this a bug, or is it just me?
Date: Tue, 06 Feb 2001 20:15:35 -0800
Message-ID: <web-1187561@davinci.ethosmedia.com> (raw)
In-Reply-To: <3A809F15.1C60699C@agliodbs.com>
Tom et al.
Discovered this quirk in foriegn keys:
In the preliminary version of a database, I added foriegn
key constraints to a number of tables, linking them to a
column in a shared reference table (status.status) that was
only one-half of a composite primary key (and thus the
values were not unique). When I tried to delete a row
containing a "2" in the status column from the status
relation, I received a Foreign Key violation error event
though there were other "2"'s in the table still present.
So ... is this a bug in forign key implementation, or just
my fault for keying off a non-unique value?
And, if the latter, is there a way I can construct a foreign
key constraint that keys onto a view or query?
Grazie!
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com
Subject: Re: Is this a bug, or is it just me?
In-Reply-To: <web-1187561@davinci.ethosmedia.com>
References: <3A809F15.1C60699C@agliodbs.com> <web-1187561@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