Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id E17D3475FF1 for ; Mon, 9 Sep 2002 14:38:59 -0400 (EDT) Received: from squire.barchord.com (squire.barchord.com [216.194.67.18]) by postgresql.org (Postfix) with ESMTP id 2F31D475FE1 for ; Mon, 9 Sep 2002 14:38:59 -0400 (EDT) Received: from [10.0.2.147] (nat.inquent.com [216.6.14.45]) by squire.barchord.com (Postfix) with ESMTP id 1CDE6492; Mon, 9 Sep 2002 14:38:59 -0400 (EDT) Subject: Re: RESTRICT / CASCADE From: Rod Taylor To: Peter Eisentraut Cc: pgsql-docs@postgresql.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 09 Sep 2002 14:39:05 -0400 Message-Id: <1031596746.268.83.camel@jester> Mime-Version: 1.0 X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/28 X-Sequence-Number: 1480 On Mon, 2002-09-09 at 14:40, Peter Eisentraut wrote: > Rod Taylor writes: > > > If the defaults are different, perhaps the documentation should show > > it's examples using RESTRICT or CASCADE explicitly? > Also, in most examples the choice between RESTRICT and CASCADE would have > to be arbitrarily made by the documentation writer and might not be what > the user really wanted to do. Good points. I suppose anyone paying enough attention to notice that our behaviour restricts where others casacade will quickly realize what they need to do. -- Rod Taylor