From: | Shruthi A <shruthi(dot)iisc(at)gmail(dot)com> |
---|---|
To: | Shoaib Mir <shoaibmir(at)gmail(dot)com>, "Wayne E(dot) Seguin" <wayneeseguin(at)gmail(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Can i force deletion of dependent rows? |
Date: | 2010-02-13 17:25:21 |
Message-ID: | 6caee9521002130925u46ac27c1u9c0c2f3f202e411f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Landscheidt | 2010-02-13 22:45:41 | Re: Can i force deletion of dependent rows? |
Previous Message | Shoaib Mir | 2010-02-13 11:32:36 | Re: Can i force deletion of dependent rows? |