Re: Cascade constraint gone!!!

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Linh Luong <linh(dot)luong(at)computalog(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Cascade constraint gone!!!
Date: 2001-06-06 17:27:00
Message-ID: Pine.BSF.4.21.0106061024020.16204-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Wed, 6 Jun 2001, Linh Luong wrote:

> I recently wipe my database away. And some of the tables have a UPDATE
> CASCADE on it to another table.
> When I reload the data from my backup that I did with pg_dumpall. My
> code started to give me an error because I tried to modify a table that
> was reference from another table. But the referenced table should have
> an UPDATE CASCADE. But according to the error it doesn't.

Hmm, what does the create constraint triggers in the dump say? And what
is in pg_trigger for the constraint?

> Is there a way to add the ON UPDATE CASCADE back without dropping any
> table again?

Well, you can manually delete the constraint triggers for this
constraint and use alter table add constraint to add the constraint again
with the appropriate actions.

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Stephan Szabo 2001-06-06 17:29:19 Re: Memory exhausted in AllocSetAlloc
Previous Message jmscott@REMOVEMEyahoo.com 2001-06-06 17:07:35 maximum number of rows in table - what about oid limits?