Re: Should this require CASCADE?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jan Wieck <JanWieck(at)Yahoo(dot)com>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Should this require CASCADE?
Date: 2002-07-11 03:33:27
Message-ID: 200207110333.g6B3XR300443@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Sounds good to me, and I don't think we need to require RESTRICT just
> > because the standard says so. Does the standard require RESTRICT for
> > every DROP or just drops that have foreign keys?
>
> Syntactically, it requires RESTRICT or CASCADE on *every* form of DROP.
> I don't think we're willing to do that...

Yuck, or RESTRICT|CASCADE yuck.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-07-11 03:41:04 Okay, how about indexes versus unique/primary constraints?
Previous Message Tom Lane 2002-07-11 03:31:20 Re: Should this require CASCADE?