From: Alvaro Herrera <alvherre@commandprompt.com>
To: Goulet, Dick <DGoulet@vicr.com>
Cc: Frank van Vugt <ftm.van.vugt@foxi.nl>
Cc: Greg Stark <gsstark@mit.edu>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Incremental results from libpq
Date: Sun, 13 Nov 2005 12:24:01 -0300
Message-ID: <20051113152401.GB31570@surnet.cl> (raw)
In-Reply-To: <4001DEAF7DF9BD498B58B45051FBEA6502EF5389@25exch1.vicorpower.vicr.com>
References: <4001DEAF7DF9BD498B58B45051FBEA6502EF5389@25exch1.vicorpower.vicr.com>
Goulet, Dick wrote:
> For a simple "select * from <table_name>" even with a where
> clause you may simply get the results one row at a time as they are
> extracted & deemed appropriate for the result set. But if you've
> included a group by or order by clause, or a union/intersect/minus
> clause then yes, the database will assemble results before sending them
> to the client.
So, what happens with the 1/x query Tom mentioned? How does Oracle
handles that situation? Notice there's no special clause in the query
itself, so if it's extracted and returned, there's no way for the server
to know that there's a problem laying ahead.
> Also Oracle supports cursors which allow you to pop one or more
> rows off of the result set at a time. The way Postgresql returns data
> all at once is different.
Postgres supports cursors too. The Qt guys, and everyone else, could be
using it to get incremental results right now, no libpq mods necessary.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
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: alvherre@commandprompt.com, DGoulet@vicr.com, ftm.van.vugt@foxi.nl, gsstark@mit.edu
Subject: Re: Incremental results from libpq
In-Reply-To: <20051113152401.GB31570@surnet.cl>
* 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