| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Viacheslav N Tararin <taras(at)dekasoft(dot)com(dot)ua> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Rule execution bug |
| Date: | 2003-09-25 18:51:47 |
| Message-ID: | 27385.1064515907@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Viacheslav N Tararin <taras(at)dekasoft(dot)com(dot)ua> writes:
> For the next schema rule "d_analysis_plan" perform only first DELETE
> statement, second statement not performed.
You did not show us the definition of "analysis_plan", but I'll bet it's
a view joining t_sub_plan and t_account_plan. If so, this is not a bug.
After the first DELETE, there is no longer anything in the view matching
the id, and so the second DELETE finds nothing to delete.
You might have better luck using ON DELETE CASCADE foreign-key
references to accomplish the results you want.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Browne | 2003-09-25 19:06:50 | Re: Postgresql 'eats' all mi data partition |
| Previous Message | Stephan Szabo | 2003-09-25 18:35:09 | Re: Postgresql 'eats' all mi data partition |