From: | Jie Liang <jliang(at)ipinc(dot)com> |
---|---|
To: | craig(dot)may(at)s2(dot)enthdimension(dot)com(dot)au |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Cascading Deletes |
Date: | 2000-09-06 18:12:50 |
Message-ID: | 39B68922.320969E9@ipinc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi, there,
2 ways may resolve you problem, I believe:
1. re_create your table set _ID as primary key and ID as foreign key with option ON
DELETE CASCADE
if _ID is unique key.
2. create a rule bind this table, for each row deleting(or create a trigger).
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
--
Jie LIANG
Internet Products Inc.
10350 Science Center Drive
Suite 100, San Diego, CA 92121
Office:(858)320-4873
jliang(at)ipinc(dot)com
www.ipinc.com
From | Date | Subject | |
---|---|---|---|
Next Message | Mads Jensen | 2000-09-06 18:34:47 | Re: Auto increment |
Previous Message | Stephan Szabo | 2000-09-06 17:50:09 | Re: Cascading Deletes |