Re: Cascading Deletes - Mailing list pgsql-sql

From Stephan Szabo
Subject Re: Cascading Deletes
Date
Msg-id Pine.BSF.4.10.10009061048330.89808-100000@megazone23.bigpanda.com
Whole thread Raw
In response to Cascading Deletes  (Craig May <craig.may@s2.enthdimension.com.au>)
List pgsql-sql
I think a references constraint on ID
referencing _ID with ON DELETE CASCADE
should do what you want.

Stephan Szabo
sszabo@bigpanda.com

On Wed, 6 Sep 2000, Craig May wrote:

> Hi,
> 
> I have a tables having this structure:
> 
> ID (int) | _ID (int) | Name (String)
> 
> 
> _ID is the parent of ID.
> 
> I'm looking for the best method to perform a cascade delete.  For example, I
> delete _ID, it in turn deletes ID, and should ID also be an entry within _ID, it
> would continue through the chain.
> 
> For example:
> 
> 0 0 Base
> 1 0 Sib1
> 2 0 Sib2
> 3 0 Sib3
> 4 1 Sib1_1
> 5 1 Sib1_2
> 
> 
> Deleting Base would remove all the entries.  Deleting Sib1 would delete Sib1_1
> and Sib1_2.
> Can anyone help out here?
> 
> Regards,
> Craig May
> 
> Enth Dimension
> http://www.enthdimension.com.au
> 



pgsql-sql by date:

Previous
From: Jie Liang
Date:
Subject: Re: Protection of tables by group and not by users
Next
From: Jie Liang
Date:
Subject: Re: Cascading Deletes