From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Lamb <slamb@slamb.org>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Incremental results from libpq
Date: Wed, 09 Nov 2005 16:22:08 -0500
Message-ID: <19391.1131571328@sss.pgh.pa.us> (raw)
In-Reply-To: <4D426B54-E08F-4DE9-9776-D46610CA4968@slamb.org>
References: <4D426B54-E08F-4DE9-9776-D46610CA4968@slamb.org>
Scott Lamb <slamb@slamb.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, slamb@slamb.org
Subject: Re: Incremental results from libpq
In-Reply-To: <19391.1131571328@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox