"Murray S. Kucherawy" <m...@cloudmark.com> writes:
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
>> This is complete nonsense. If you followed the documented method for
>> using PQgetResult -- ie, keep calling it till it returns NULL, rather
>> than assuming there will be a specific number of results --- then
>> PQstatus would show you the bad status afterwards.
> Your assertion here of "Read the result set to exhaustion, THEN check
> connection status to see if it was bad to begin with," can be politely
> described as counter-intuitive.
[ shrug... ] I guess if your intuition is that PQstatus should be
expected to intuit the failure of a call that hasn't happened yet,
then it's counter-intuitive.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
