Re: referencial integrity constraint bug in version 7.0 beta 5 - Mailing list pgsql-general

From Bruce Momjian
Subject Re: referencial integrity constraint bug in version 7.0 beta 5
Date
Msg-id 200004281444.KAA28255@candle.pha.pa.us
Whole thread Raw
In response to Re: referencial integrity constraint bug in version 7.0 beta 5  (wieck@debis.com (Jan Wieck))
List pgsql-general
Done and updated.


> Spyros Vasileiadis wrote:
>
> > I am running a slackware 7 linux box (kernel 2.2.14 g++2.91.66) and i 've
> > installed the ver 7 beta 5. So i had the following problem
> >
> > I suppose when you make a constraint statement for reference key theere
> > should be a check for the fields names , example:
>
>     You're  right. Bruce, would you please add these items to the
>     7.1 todo:
>
>         Check PK attributes to exist (maybe to be comparable with
>         corresponding  FK  attribute  if possible) at foreign key
>         definition time.
>
>         Deny column dropping if column in question is used by  an
>         FK constraint.
>
>         Propagate column or table renaming to FK constraints.
>
>         Emit  a  warning  if  at FK creation time no UNIQUE index
>         exists over referenced PK attributes.
>
>
> Jan
>
> --
>
> #======================================================================#
> # It's easier to get forgiveness for being wrong than for being right. #
> # Let's break this rule - forgive me.                                  #
> #========================================= wieck@debis.com (Jan Wieck) #
>
>
>


--
  Bruce Momjian                        |  http://www.op.net/~candle
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Hierarchy indicies
Next
From: Bruce Momjian
Date:
Subject: Re: Revisited: Transactions, insert unique.