Re: Dropped table screws referential integrity? - Mailing list pgsql-admin

From Joel Burton
Subject Re: Dropped table screws referential integrity?
Date
Msg-id Pine.LNX.4.30.0203071407500.21737-100000@temp.joelburton.com
Whole thread Raw
In response to Re: Dropped table screws referential integrity?  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
List pgsql-admin
On Thu, 7 Mar 2002, Stephan Szabo wrote:

>
> On Thu, 7 Mar 2002, Joel Mc Graw wrote:
>
> > I had a table (job_documents) that referenced another (jobs).  I no
> > longer needed job_documents, so I dropped it.  Now, any attempt to
> > delete rows from jobs fails--it complains that job_documents doesn't
> > exist.  Is there a way to fix this?
>
> You'll need to find the two triggers on jobs that reference job_documents
> (do a select * from pg_trigger and look at the argument list to find
> them) and drop them and you should be fine.

In techdocs.postgresql.org, I have a HOWTO on referential integrity that
provides some views that make it easier to find the ref rules in effect in
your tables. These are helpful for debugging.

--

Joel BURTON  |  joel@joelburton.com  |  joelburton.com  |  aim: wjoelburton
Independent Knowledge Management Consultant


pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Dropped table screws referential integrity?
Next
From: Jeff Self
Date:
Subject: Re: Fw: --fast switch