Re: Dropped table screws referential integrity?

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(at)joelburton(dot)com | joelburton.com | aim: wjoelburton
Independent Knowledge Management Consultant