David Rysdam wrote:
> 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.
I think you should return to Sybase as soon as you can! :-)
Seriously, look at the current TODO list and the issues involved.
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
In response to
pgsql-interfaces by date
|Next:||From: Bruce Momjian||Date: 2005-11-22 22:33:18|
|Subject: Re: Not clear on what PQgetResult does|
|Previous:||From: CSN||Date: 2005-11-22 08:49:32|
|Subject: Re: ruby/postgres - getting assoc array of rows?|