Re: Rule updates and PQcmdstatus() issue - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: Rule updates and PQcmdstatus() issue
Date
Msg-id 1031624432.51452.4.camel@jester
Whole thread Raw
In response to Re: Rule updates and PQcmdstatus() issue  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Mon, 2002-09-09 at 22:11, Bruce Momjian wrote:
> Jan Wieck wrote:
> > We should surely keep this on a much more technical level and avoid any
> > personal offendings. To do so, please explain to me why you think that
> > triggers and constraints are out of focus here? What is the difference
> > between a trigger, a rule and an instead rule from a business process
> > oriented point of view? I think there is none at all. They are just
> > different techniques to do one and the same, implement business logic in
> > the database system.
> 
> All the problems here are coming from INSTEAD rules.  We don't have
> INSTEAD triggers or contraints.

Well.. Triggers could be exclusively INSTEAD.  A trigger could easily
write a few things to a number of other tables, and return NULL in a
BEFORE trigger which would prevent execution of the requested command.



--  Rod Taylor



pgsql-hackers by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Rule updates and PQcmdstatus() issue
Next
From: Bruce Momjian
Date:
Subject: Re: Proposal: Solving the "Return proper effected tuple