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

From Tom Lane
Subject Re: Should this require CASCADE?
Date
Msg-id 29811.1026405366@sss.pgh.pa.us
Whole thread Raw
In response to Re: Should this require CASCADE?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Should this require CASCADE?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Should this require CASCADE?  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Now, if someone wanted to say CASCADE|RESTRICT was
> required for DROP _only_ if there is some foreign key references to the
> table, I would be OK with that, but that's not what the standard says.

But in fact that is not different from what I propose to do.  Consider
what such a rule really means:* if no dependencies exist for the object, go ahead and delete.* if dependencies exist,
complain.
How is that different from "the default behavior is RESTRICT"?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Should this require CASCADE?
Next
From: "Groff, Dana"
Date:
Subject: Re: Should this require CASCADE?