Re: Should this require CASCADE? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Should this require CASCADE?
Date
Msg-id 6164.1026354007@sss.pgh.pa.us
Whole thread Raw
In response to Re: Should this require CASCADE?  (Jan Wieck <JanWieck@Yahoo.com>)
Responses Re: Should this require CASCADE?  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
List pgsql-hackers
Jan Wieck <JanWieck@Yahoo.com> writes:
> I think the idea was to have it default to CASCADE for this release, not
> to break existing code right away.

I never thought that.  If we default to CASCADE then a DROP is likely to
delete stuff that it would not have deleted in prior releases.  That
seems *far* more dangerous than "breaking existing code".  I doubt
there's much existing code that does automatic DROPs anyway, at least
of things that might have dependencies.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: [INTERFACES] [pgaccess-users] RE:
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Re: Should this require CASCADE?