Received: from localhost.localdomain (postgresql.org [64.49.215.8])
	by localhost (Postfix) with ESMTP id 8BBBE476FFE
	for <pgsql-sql@postgresql.org>; Fri, 14 Jun 2002 12:06:35 -0400 (EDT)
Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250])
	by postgresql.org (Postfix) with ESMTP id BC3C64772A7
	for <pgsql-sql@postgresql.org>; Fri, 14 Jun 2002 12:05:14 -0400 (EDT)
Received: from [63.195.55.98] (account <josh@agliodbs.com>)
	by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.9)
	with HTTP id 1527480; Fri, 14 Jun 2002 09:05:19 -0700
From: "Josh Berkus" <josh@agliodbs.com>
Subject: Re: ON DELETE CASCADE question
To: Wei Weng <wweng@kencast.com>, pgsql-sql@postgresql.org
X-Mailer: CommuniGate Pro Web Mailer v.3.5.9
Date: Fri, 14 Jun 2002 09:05:19 -0700
Message-ID: <web-1527480@davinci.ethosmedia.com>
In-Reply-To: <1024062044.32682.5.camel@Monet>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Archive-Number: 200206/208
X-Sequence-Number: 8173

Wei,

> Does ON DELETE CASCADE attribute you specify in CREATE TABLE
> statement
> actually create triggers for every foreign key it refers to?
>

Yes.  Two triggers for each key, I think.

-Josh