| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, Steve Howe <howe(at)carcass(dot)dhs(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Rule updates and PQcmdstatus() issue |
| Date: | 2002-09-10 02:20:31 |
| Message-ID: | 1031624432.51452.4.camel@jester |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vanmunin Chea | 2002-09-10 02:23:45 | If there a bug in the psql or just a feature . |
| Previous Message | Stephan Szabo | 2002-09-10 02:18:07 | Re: Rule updates and PQcmdstatus() issue |