Re: Rule updates and PQcmdstatus() issue

Hello Jan,

Monday, September 9, 2002, 11:15:47 AM, you wrote:

JW> Steve Howe wrote:
>> 
>> Hello all,
>> 
>> PostgreSQL *still* has a bug where PQcmdStatus() won't return the
>> number of rows updated. But that is essential for applications, since
>> without it of course we don't know if the updates/delete/insert
>> commands succeded. Even worst, on interfaces like Delphi/dbExpress the
>> program will return an error message and rollback transaction thinking
>> nothing have been updated. In other words, unusable.
>> 
>> This render views useless (I either use view with rules and don't get
>> my program working) and won't allow me to proper use security settings
>> on PostgreSQL...
>> 
>> This is a *major* issue in my opinion that appeared on a May thread
>> but I can't see it done on version 7.2.2. Even worst, I can't see
>> nothing on the TODO file.
>> 
>> Will this fix finally  appear on 7.3 ? Any ways to work around this ?
>> How can I know at least if *something* succeeded, or how many rows
>> (the proper behavior)?

JW> And of course, in the case you insert into a real table you expect if a
JW> trigger procedure suppressed your original INSERT, but fired a cascade
JW> of other triggers by doing a mass UPDATE somewhere else instead, that
JW> all these caused UPDATEs and whatnot's are summed up and returned
JW> instead, right? Or what is proper behavior here?
What is documented, and what is expected: PQcmdStatus(),
PQcmdTuples()and PQoidValue() returning the information they should be.

JW> So please, "proper behavior" is not allways what your favorite tool
JW> expects. And just because you cannot "fix" your tool doesn't make that
JW> behavior any more "proper".
Do you have any word more appropriate ?

And just so that you know, I can't "fix" my tool because I have other
job to do (and a lot of that and that job uses PostgreSQL), and
unhappily I couldn't join the development team and thus I'm not aware
of how it works internally. The reason isn't that I just don't have
intellectual capacity.

And it looks like *you* overhauled the query rewrite rule system, so
what we are talking is something that must have passed through you. So
instead of offending me, your "proper" behavior would be try to help
and suggest a solution for the problem, as other developers are doing.

Thanks again.

------------- 
Best regards,Steve Howe                           mailto:howe@carcass.dhs.org