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)?
And of course, in the case you insert into a real table you expect if a
trigger procedure suppressed your original INSERT, but fired a cascade
of other triggers by doing a mass UPDATE somewhere else instead, that
all these caused UPDATEs and whatnot's are summed up and returned
instead, right? Or what is proper behavior here?
So please, "proper behavior" is not allways what your favorite tool
expects. And just because you cannot "fix" your tool doesn't make that
behavior any more "proper".
Jan
>
> Thank you very much.
>
> -------------
> Best regards,
> Steve Howe mailto:howe@carcass.dhs.org
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
