Skip site navigation (1) Skip section navigation (2)

Re: Incremental results from libpq

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Lamb <slamb(at)slamb(dot)org>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Incremental results from libpq
Date: 2005-11-09 21:22:08
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
Scott Lamb <slamb(at)slamb(dot)org> writes:
> Is there a better way?

Not at the moment.  It's been requested before though, so if you want to
develop a patch for libpq, have at it.

The main reason why libpq does what it does is that this way we do not
have to expose in the API the notion of a command that fails part way
through.  If you support partial result fetching then you'll have to
deal with the idea that a SELECT could fail after you've already
returned some rows to the client.  I am not sure that this is a huge
deal, but it definitely uglifies the API a bit.  It would be a good
idea to think through exactly what clients will need to do to cope with
that fact before you start designing the API extension.

			regards, tom lane

In response to


pgsql-interfaces by date

Next:From: Scott LambDate: 2005-11-09 22:09:09
Subject: Re: Incremental results from libpq
Previous:From: Scott LambDate: 2005-11-09 19:36:29
Subject: Incremental results from libpq

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group