> > 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'm wondering, what kind of failure do you have in mind, here? If I'm informed
correctly then Oracle and others are generating the complete static result
set on the server-side, which will then stay cached until all rows/chunks are
fetched. The one failure that comes to mind in this scenario is that the
connection breaks down, but since informing the client would then be a bit
difficult, you'll certainly be referring to something else ;)
If PostgreSQL were to build the complete result-set before handing over the
first fetched rows/chunks, then I understand. Is that the case? Or something
else even...?
--
Best,
Frank.
