Received: from mail.com-stock.com (mail.com-stock.com [204.255.137.254]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f7NEcWP78921 for ; Thu, 23 Aug 2001 10:38:32 -0400 (EDT) (envelope-from gregw@com-stock.com) Received: by mail.com-stock.com (Postfix, from userid 1000) id 27D25105; Thu, 23 Aug 2001 10:38:24 -0400 (EDT) Received: from deimos (deimos.com-stock.com [204.255.137.120]) by mail.com-stock.com (Postfix) with SMTP id CD3A3D9F2; Thu, 23 Aug 2001 10:38:21 -0400 (EDT) Message-ID: <003301c12be2$a72afc60$7889ffcc@comstock.com> From: "Gregory Wood" To: "Jan Wieck" Cc: "PostgreSQL-General" References: <200108231355.f7NDtb301413@jupiter.us.greatbridge.com> Subject: Re: protected ON DELETE CASCADE Date: Thu, 23 Aug 2001 10:48:19 -0400 Organization: Comstock Net Services MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Archive-Number: 200108/717 X-Sequence-Number: 14114 > key constraint is ON DELETE NO ACTION, which confusingly > enough aborts the transaction (it's defined that way in the > SQL standard, don't ask me why they called it NO ACTION). NO ACTION because it takes no action on the child record? Makes sense when you consider that otherwise you either CASCADE the delete to the child or SET NULL for the child. Greg