From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200511222233.jAMMXI925739@candle.pha.pa.us>
Subject: Re: Not clear on what PQgetResult does
In-Reply-To: <20051117211635.GD10976@surnet.cl>
To: Alvaro Herrera <alvherre@commandprompt.com>
Date: Tue, 22 Nov 2005 17:33:18 -0500 (EST)
CC: David Rysdam <drysdam@ll.mit.edu>, pgsql-interfaces@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Alvaro Herrera wrote:
> 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.
> 
> If you are in need of partial results you may as well use a cursor and
> fetch from it, a bunch at a time.

Right, this is the standard way.

> > Or are there underlying server reasons why this won't work?
> 
> This topic was discussed four days ago I think ... look for a thread
> with subject "Incremental results from libpq" on the archives of this
> list.

That thread has already been condensed into a TODO entry.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073