> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Tom Lane > Sent: Sunday, May 12, 2002 12:30 PM > To: Rod Taylor > Cc: Hackers List > Subject: Re: [HACKERS] TRUNCATE > > > "Rod Taylor" <[EMAIL PROTECTED]> writes: > > I'm thinking it should check for an on delete rule as well as user > > triggers. > > Seems reasonable to me. > > Should there be a "FORCE" option to override these checks and do it > anyway? Or is that just asking for trouble?
I've relied on being able to TRUNCATE w/o having RI kick in to lots of data clean ups, forced sorts, etc. I'd find it annoying if I couldn't do this anymore (or had to do equally-annoying things, like manually drop then recreate the triggers, etc.) 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. - J. Joel BURTON | [EMAIL PROTECTED] | joelburton.com | aim: wjoelburton Knowledge Management & Technology Consultant ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
