Re: Get constrrelid for fk constraints that lost it - Mailing list pgsql-patches

From Stephan Szabo
Subject Re: Get constrrelid for fk constraints that lost it
Date
Msg-id 20020930091319.N81475-100000@megazone23.bigpanda.com
Whole thread Raw
In response to Re: Get constrrelid for fk constraints that lost it  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
On Mon, 30 Sep 2002, Tom Lane wrote:

> Stephan Szabo <sszabo@megazone23.bigpanda.com> writes:
> >> (We can tweak the RI triggers to make the runtime failure message be
> >> more helpful than "Relation 0 not found".)  ISTM the point of having
>
> > Are we mostly concerned about the case where it's 0 or all cases
> > where the constrrelid relation doesn't open?
>
> I'd only special-case OID 0; we can reasonably assume that came from
> a broken CREATE CONSTRAINT TRIGGER definition.  Any other failure is

What do we want to tell the user?  I was thinking we could give something
like:

 Trigger "blah" has no target table. You will need to remove the
triggers for this foreign key constraint and add the constraint again
using ALTER TABLE ADD CONSTRAINT.



pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Get constrrelid for fk constraints that lost it
Next
From: Peter Eisentraut
Date:
Subject: Re: tweak CREATE SEQUENCE grammar