> could you please make a complete table of all
> possible situations and the expected returns? With complete I mean
> including all combinations of rules, triggers, deferred constraints and
> the like. Or do you at least see now where in the discussion we got
> stuck?

Imho only view rules (== instead rules) should affect the returned info.
Not "non instead" rules, triggers or constraints. Those are imho supposed to 
be transparent as long as they don't abort the statement. 

Especially for triggers and constraints there is no room for flexibility,
since other db's also don't modify the "affected rows" count for these.
Think sqlca.sqlerrd[2] /* number of rows processed */!

Andreas

Mon, 9 Sep 2002 17:48:09 +0200
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>
Re: Rule updates and PQcmdstatus() issue