From: | David Rysdam <drysdam(at)ll(dot)mit(dot)edu> |
---|---|
To: | |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Not clear on what PQgetResult does |
Date: | 2005-11-17 20:42:54 |
Message-ID: | 437CEB4E.5040402@ll.mit.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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?
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-11-17 21:16:35 | Re: Not clear on what PQgetResult does |
Previous Message | Joshua D. Drake | 2005-11-17 20:40:34 | Re: Not clear on what PQgetResult does |