Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 5560D632B8E
	for <pgsql-sql-postgresql.org@mail.postgresql.org>;
	Sat, 13 Feb 2010 13:25:33 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia,
	port 10024) with ESMTP id 09029-03 for
	<pgsql-sql-postgresql.org@mail.postgresql.org>;
	Sat, 13 Feb 2010 17:25:12 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-iw0-f186.google.com (mail-iw0-f186.google.com
	[209.85.223.186])
	by mail.postgresql.org (Postfix) with ESMTP id 905386329C6
	for <pgsql-sql@postgresql.org>; Sat, 13 Feb 2010 13:25:22 -0400 (AST)
Received: by iwn16 with SMTP id 16so4244457iwn.10
	for <pgsql-sql@postgresql.org>; Sat, 13 Feb 2010 09:25:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:message-id:subject:from:to:content-type;
	bh=lHLtSObxBfKre9NxQES9QJQ3XQhiuPC6UzUB9e/kQSo=;
	b=qE26NGr0Q8oCY313WQuvcYDUdOEKaQQW6ZaSn1kPCC9NGCVadowBfzAOfMpEwjJBPy
	hXJsKKKedG9QJ4aTJTofN1Gd4JWvbtBA5saWE3O7dQV+2jyiPPAXNRnJ+Qtg1CJGZw8q
	TfTXHOIRlsajjAjioww678mMf95OGwxhV+m24=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	b=Q5WAxP7LpCI8t4rX16bWLs3mLUw3bcx5kH4eWCuls6Q+FLz4IeShhyUyv95xaYunHn
	w8YaYRZ8UnuGn0GXXZtBwrMEVDBhMC6VpAkkw9ZkVGs7eww/pX+ukmfenxBaCAx3k+tD
	1BAY6fU4U83q9L5c/KuSjr+etV3qYB4pRoqAE=
MIME-Version: 1.0
Received: by 10.231.161.143 with SMTP id r15mr3267889ibx.62.1266081921559;
	Sat, 13 Feb 2010 09:25:21 -0800 (PST)
In-Reply-To: <bf54be871002130332h6617b33ateb4dcef3d4213054@mail.gmail.com>
References: <6caee9521002120424l27ec8d3eq3b69522d0a773686@mail.gmail.com>
	<6caee9521002122211q7e4fd2fcj1a0489fd64dc204a@mail.gmail.com>
	<m3fx55linc.fsf@passepartout.tim-landscheidt.de>
	<ef3e5d51002130323j13d32159we970a665ec8a0190@mail.gmail.com>
	<bf54be871002130332h6617b33ateb4dcef3d4213054@mail.gmail.com>
Date: Sat, 13 Feb 2010 22:55:21 +0530
Message-ID: <6caee9521002130925u46ac27c1u9c0c2f3f202e411f@mail.gmail.com>
Subject: Re: Can i force deletion of dependent rows?
From: Shruthi A <shruthi.iisc@gmail.com>
To: Shoaib Mir <shoaibmir@gmail.com>,
	"Wayne E. Seguin" <wayneeseguin@gmail.com>, pgsql-sql@postgresql.org
Content-Type: multipart/alternative; boundary=001636c5c07530ec6d047f7eab64
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.935 tagged_above=-10 required=5 tests=AWL=0.663,
	BAYES_00=-2.599, HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 201002/54
X-Sequence-Number: 33653

--001636c5c07530ec6d047f7eab64
Content-Type: text/plain; charset=ISO-8859-1

Thanks people, but the trigger doesnt really solve my problem.  You see,
there is actually a CHAIN of dependencies where B references A, C references
B, D and E reference C and so on...   So if i start writing triggers for all
these, there'll be a huge process to follow.  I'm not strictly against it, i
might use it as a last resort, but i'm asking if a simple DML statement
would solve my problem.

Dear Shoaib, I did mention in a note that I don't want to recreate the 2
tables with the 'on delete cascade' clause.  The tables are ALREADY created
and populated.  And they are huge.  So i cannot afford to drop and recreate
them.  I want an option in DML only.  If that is possible that is.


Thanks,
Shruthi

--001636c5c07530ec6d047f7eab64
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks people, but the trigger doesnt really solve my problem.=A0 You see, =
there is actually a CHAIN of dependencies where B references A, C reference=
s B, D and E reference C and so on...=A0=A0 So if i start writing triggers =
for all these, there&#39;ll be a huge process to follow.=A0 I&#39;m not str=
ictly against it, i might use it as a last resort, but i&#39;m asking if a =
simple DML statement would solve my problem.<br>
<br>Dear Shoaib, I did mention in a note that I don&#39;t want to recreate =
the 2 tables with the &#39;on delete cascade&#39; clause.=A0 The tables are=
 ALREADY created and populated.=A0 And they are huge.=A0 So i cannot afford=
 to drop and recreate them.=A0 I want an option in DML only.=A0 If that is =
possible that is.<br>
<br><br>Thanks,<br>Shruthi<br>

--001636c5c07530ec6d047f7eab64--