Re: TRUNCATE - Mailing list pgsql-hackers

From nconway@klamath.dyndns.org (Neil Conway)
Subject Re: TRUNCATE
Date
Msg-id 20020513042422.GA29053@klamath.dyndns.org
Whole thread Raw
In response to Re: TRUNCATE  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Responses Re: TRUNCATE  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
List pgsql-hackers
On Mon, May 13, 2002 at 10:17:07AM +0800, Christopher Kings-Lynne wrote:
> > I'm happy w/o the FORCE option (just let TRUNCATE do it), but if enough
> > people think that the FORCE keyword should be added to allow overriding of
> > triggers, that could be a good compromise.
> >
> > But, please, don't take away the ability to TRUNCATE. Doing it when there
> > are triggers is one the strengths of TRUNCATE, IMNSHO.
> 
> It seems to me that there's more and more need for an 'SET CONSTRAINTS
> DISABLED' and 'SET CONSTRAINTS ENABLED' command that affects only foreign
> keys.

I really dislike the idea of referring to "constraints" but only affecting
foreign key constraints.

And what would be the security/data-integrity ramifications of allowing
this?

Cheers,

Neil

-- 
Neil Conway <neilconway@rogers.com>
PGP Key ID: DB3C29FC


pgsql-hackers by date:

Previous
From: "Joel Burton"
Date:
Subject: Re: TRUNCATE
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Re: TRUNCATE