pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <janwieck@Yahoo.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: sqllist <pgsql-sql@postgresql.org>
Subject: Re: Is this a bug, or is it just me?
Date: Thu, 8 Feb 2001 05:59:12 -0500 (EST)
Message-ID: <200102081059.FAA02777@jupiter.greatbridge.com> (raw)
In-Reply-To: <web-1187561@davinci.ethosmedia.com>

Josh Berkus wrote:
> 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?

    The referenced columns of a foreign key constraint shall have
    a unique constraint. That's how it is in the SQL  specs.   So
    it  is a bug that the system let's you specify the constraint
    at all. I think Stephan fixed it for 7.1.

    OTOH Postgres  doesn't  (and  shouldn't)  enforce  it  after,
    because  if  it  would,  you couldn't drop/create a corrupted
    index.

    And no, you can't actually reference to a  view  or  anything
    else  than a table. That is, because the system wouldn't know
    how to check for the DELETE/UPDATE cases on the  base  tables
    building  the  view  if  the  removal  of a key would violate
    existing references.

    For such custom setups,  we  have  procedural  languages  and
    triggers.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




view thread (3+ messages)

Message-ID: <200102081059.FAA02777@jupiter.greatbridge.com>
Permalink:  ../200102081059.FAA02777@jupiter.greatbridge.com/
Also on:    postgresql.org/message-id/200102081059.FAA02777@jupiter.greatbridge.com

 · 

reply

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: janwieck@Yahoo.com, josh@agliodbs.com
  Subject: Re: Is this a bug, or is it just me?
  In-Reply-To: <200102081059.FAA02777@jupiter.greatbridge.com>
  References: <web-1187561@davinci.ethosmedia.com> <200102081059.FAA02777@jupiter.greatbridge.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