Re: Not clear on what PQgetResult does - Mailing list pgsql-interfaces

From David Rysdam
Subject Re: Not clear on what PQgetResult does
Date
Msg-id 437CEB4E.5040402@ll.mit.edu
Whole thread Raw
In response to Re: Not clear on what PQgetResult does  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Not clear on what PQgetResult does  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Not clear on what PQgetResult does  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Not clear on what PQgetResult does  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Not clear on what PQgetResult does  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-interfaces
Joshua D. Drake wrote:

>>
>>>
>>> It isn't.  You can use it in an asynchronous client, but the way you do
>>> that is by not calling it until PQisBusy says you can (which means the
>>> whole result has arrived, and you're just calling PQgetResult to get
>>> hold of it).
>>>
>> So there's no way to have libpq return partial results before they 
>> are all ready?
>>
>> If I may, I would like to express some degree of incredulity.  Even 
>> the version of Sybase I'm using does this right and it's from 1997!
>
> I am sure we would welcome a patch ;))

To be honest, this is almost enough to drive me away from PG.  But I 
like everything else about it, so I could perhaps give a patch a whirl.  
Or are there underlying server reasons why this won't work?


pgsql-interfaces by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Not clear on what PQgetResult does
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Not clear on what PQgetResult does