Subject: Re: Need help creating a BEFORE DELETE trigger
From: Rod Taylor <rbt@rbt.ca>
To: Michael A Nachbaur <mike@nachbaur.com>
Cc: pgsql-sql@postgresql.org
In-Reply-To: <200306301445.06935.mike@nachbaur.com>
References: <200306301445.06935.mike@nachbaur.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-WvVD4XXrF7gnhubKjvLB"
Message-Id: <1057020087.28657.106.camel@jester>
Mime-Version: 1.0
Date: 01 Jul 2003 00:41:28 +0000

--=-WvVD4XXrF7gnhubKjvLB
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

> The problem I'm looking at is: could this cause a recursion problem, wher=
e the=20
> cascading deletion will try to cause the whole thing to cascade again?  H=
ow

It will only be able to delete the row (and cascade) once per row.  The
second time it tries to find the row, the row won't exist anymore.
--=20
Rod Taylor <rbt@rbt.ca>

PGP Key: http://www.rbt.ca/rbtpub.asc

--=-WvVD4XXrF7gnhubKjvLB
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQA/ANi36DETLow6vwwRAucyAJ9CKMYQBDlZwPOUEShXW54q9Pm9dQCfZWrW
RajxiAV1cK+Ixn9LWF4wKJc=
=wTkP
-----END PGP SIGNATURE-----

--=-WvVD4XXrF7gnhubKjvLB--