From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | andrew(at)pillette(dot)com |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: CREATE RULE ignored, what did I do wrong |
Date: | 2004-09-11 06:42:23 |
Message-ID: | 7805.1094884943@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
andrew(at)pillette(dot)com writes:
> Foreign-key constraints:
> "$1" FOREIGN KEY (smoothing_id) REFERENCES smoothing_algorithm(smoothing_id) ON UPDATE CASCADE ON DELETE CASCADE
> Rules:
> del_smoothed_rank_episode AS ON DELETE TO smoothed_rank_episode
> WHERE (NOT old.is_deleted) DO INSTEAD ...
The DELETE commands generated by the foreign key ON DELETE CASCADE will
get rewritten by your ON DELETE rule. You probably do not want to do
this; or at least not make it an INSTEAD rule.
There has been some debate in the past about whether rules should be
able to break foreign-key constraints, but I tend to class it as a
"you should know what you're doing" feature. Preventing this kind
of error would inevitably result in a serious reduction of the power
of the rule feature.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Glaesemann | 2004-09-11 12:57:23 | Re: HOW TO HANDLE ZEROS IN DATE FIELD? |
Previous Message | Michalis Kabrianis | 2004-09-11 06:22:36 | Re: [SQL] PL/pgSQL Function Problem |