Re: Adding ON UPDATE CASCADE to an existing foreign key - Mailing list pgsql-general

From Stephan Szabo
Subject Re: Adding ON UPDATE CASCADE to an existing foreign key
Date
Msg-id 20060504091559.H56325@megazone.bigpanda.com
Whole thread Raw
In response to Adding ON UPDATE CASCADE to an existing foreign key constraint  (Rich Doughty <rich@opusvl.com>)
Responses Re: Adding ON UPDATE CASCADE to an existing foreign key  (Rich Doughty <rich@opusvl.com>)
List pgsql-general
On Thu, 4 May 2006, Rich Doughty wrote:

> I have a foreign key constraint that I'd like to alter. I'd rather not
> drop and re-create it due to the size of the table involved. All I need
> to do is add an ON UPDATE CASCADE.
>
> Is it ok to set confupdtype to 'c' in pg_constraint (and will this be
> all that's needed) or is it safer to drop and recreate the constraint?

I don't think that's going to work, you'd probably need to change the
function associated with the trigger involved too.  It's probably safer to
do the drop and create.

pgsql-general by date:

Previous
From: Rich Doughty
Date:
Subject: Adding ON UPDATE CASCADE to an existing foreign key constraint
Next
From: "Sebastian Wagner"
Date:
Subject: Googles sommer of Code 2005 - Postgres Project Proposal - where to discuss? who is responsible? who can mentor?