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

From Zeugswetter Andreas SB SD
Subject Re: Rule updates and PQcmdstatus() issue
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA4961E7B@m0114.s-mxs.net
Whole thread Raw
In response to Rule updates and PQcmdstatus() issue  (Steve Howe <howe@carcass.dhs.org>)
List pgsql-hackers
> 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.

The difference is how other db's work. They all ignore triggers and constraints
in the sqlca.sqlerrd[2] "number of processed rows" count, that I see identical to our
affected rows count. They all have views, but not many have rules :-) Pg's "instead rules"
are the toolkit for views, and as such need special handling, imho.

Andreas


pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: Proposal: Solving the "Return proper effected tuple
Next
From: Karel Zak
Date:
Subject: Re: PREPARE code notes