Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6])
	by hub.org (8.9.2/8.9.1) with ESMTP id KAA57689
	for <pgsql-interfaces@postgreSQL.org>;
	Tue, 16 Feb 1999 10:48:03 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA27459;
	Tue, 16 Feb 1999 10:47:22 -0500 (EST)
To: Matthew Hagerty <matthew@venux.net>
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Methods for stepping through results? 
In-reply-to: Your message of Mon, 15 Feb 1999 22:20:58 -0500
	<4.1.19990215221328.0097ae10@mail.venux.net>
Date: Tue, 16 Feb 1999 10:47:21 -0500
Message-ID: <27457.919180041@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Matthew Hagerty <matthew@venux.net> writes:
> Is there any way to do the following:
> 1.  Return a query in groups of x (i.e. 10 or 20) and progressively return
> result groups of x.  Just think of search engine navigation.

DECLARE CURSOR ... FETCH ...

There has been some talk of providing a facility for this inside libpq,
where it could be used for handling the results of an ordinary SELECT.
But it doesn't seem real high priority, given that you can use a cursor.

> 2.  I have a client who wants to be able to select certain rows (tuples) of
> a result and then "re-submit" the query and have only those rows selected
> in the new results.  For example, if a query returns 10 rows and rows
> 2,4,7,9 are checked, when re-submitted only rows 2,4,7,9 would be returned.
>  I know it is kind of stupid, but I have to please the customer :(

Seems like something you should be handling inside your application.
Why would you "re-submit" the same query in the first place, if you
already have the results?

			regards, tom lane