| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Get constrrelid for fk constraints that lost it |
| Date: | 2002-09-30 16:19:09 |
| Message-ID: | 20020930091319.N81475-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Mon, 30 Sep 2002, Tom Lane wrote:
> Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-09-30 21:42:20 | Re: tweak CREATE SEQUENCE grammar |
| Previous Message | Tom Lane | 2002-09-30 15:24:20 | Re: Get constrrelid for fk constraints that lost it |