X-Original-To: pgsql-sql@postgresql.org
Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 327AD475A1E
	for <pgsql-sql@postgresql.org>; Thu,  6 Feb 2003 15:19:18 -0500 (EST)
Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178])
	by postgresql.org (Postfix) with ESMTP id B6A58475A37
	for <pgsql-sql@postgresql.org>; Thu,  6 Feb 2003 15:19:17 -0500 (EST)
Received: by megazone.bigpanda.com (Postfix, from userid 1001)
	id 2F318D611; Thu,  6 Feb 2003 12:19:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by megazone.bigpanda.com (Postfix) with ESMTP
	id 24E565C02; Thu,  6 Feb 2003 12:19:13 -0800 (PST)
Date: Thu, 6 Feb 2003 12:19:13 -0800 (PST)
From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: Matthew Nuzum <cobalt@bearfruit.org>
Cc: <pgsql-sql@postgresql.org>
Subject: Re: changing referential integrety action on existing table
In-Reply-To: <006c01c2ce15$8a825eb0$6900a8c0@mattspc>
Message-ID: <20030206121737.F41355-100000@megazone23.bigpanda.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200302/132
X-Sequence-Number: 11530

On Thu, 6 Feb 2003, Matthew Nuzum wrote:

> I have a table that uses the NO ACTION action for it's referential
> integrity.  I'd like to change it to CASCADE for the ON DELETE event.
> I'm using Postgres 7.2.

I think the best way is to drop all three triggers for the constraint and
use alter table add constraint to add the constraint again withe the
options you want.