Re: DO INSTEAD and conditional rules - Mailing list pgsql-hackers

From David Wheeler
Subject Re: DO INSTEAD and conditional rules
Date
Msg-id a8d72cf4fc7867a60b5362dc4dabc64e@kineticode.com
Whole thread Raw
In response to Re: DO INSTEAD and conditional rules  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
On Apr 26, 2005, at 5:02 PM, Jan Wieck wrote:

> The multi-action rules usually come into play when someone attempts to 
> make join-views updatable. Not an easy problem, granted, but most of 
> the time I have found a combination of rules together with ON 
> UPDATE/DELETE CASCADE constraints or even user defined triggers 
> absolutely sufficient. The INSERT and UPDATE case is handled by rules 
> as usual. And in the DELETE case the rule just deletes the critical 
> rows and the ON DELETE CASCADE constraints do the rest.

Yes, this is what I'm finding, too. But it would be good if the 
documentation better reflected that this is how it works.

Regards,

David



pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Disable large objects GUC
Next
From: Tom Lane
Date:
Subject: Re: [proposal] protocol extension to support loadable stream filters