Re: Incremental results from libpq - Mailing list pgsql-interfaces

From Alvaro Herrera
Subject Re: Incremental results from libpq
Date
Msg-id 20051113152401.GB31570@surnet.cl
Whole thread Raw
In response to Re: Incremental results from libpq  ("Goulet, Dick" <DGoulet@vicr.com>)
Responses Re: Incremental results from libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Incremental results from libpq  (Greg Stark <gsstark@mit.edu>)
List pgsql-interfaces
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.


pgsql-interfaces by date:

Previous
From: "Goulet, Dick"
Date:
Subject: Re: Incremental results from libpq
Next
From: Tom Lane
Date:
Subject: Re: Incremental results from libpq