Received: from cr322781-a.ym1.on.wave.home.com (cr322781-a.ym1.on.wave.home.com [24.112.37.89]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eAFHPPs17760; Wed, 15 Nov 2000 12:25:25 -0500 (EST) (envelope-from svanegmond@bang.dhs.org) Received: from svanegmond by cr322781-a.ym1.on.wave.home.com with local (Exim 3.16 #1 (Debian)) id 13w6JA-0006gi-00; Wed, 15 Nov 2000 12:25:16 -0500 Date: Wed, 15 Nov 2000 12:25:16 -0500 To: Josh Berkus Cc: sqllist , phpp Subject: Re: Re: [SQL] FTI, paged, ranked searching and efficiency. Message-ID: <20001115122516.B25685@bang.dhs.org> Reply-To: svanegmond@home.com References: <3A36DC72@operamail.com> <3A12C1DA.D296628C@agliodbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A12C1DA.D296628C@agliodbs.com>; from josh@agliodbs.com on Wed, Nov 15, 2000 at 09:03:22AM -0800 From: Stephen van Egmond X-Archive-Number: 200011/16 X-Sequence-Number: 24 Josh Berkus (josh@agliodbs.com) wrote: > Unfortunately, your only real option I can see for DB server-side row > grabbing is: Create the query(ies) as a temporary table or view using a > function. Then use Limit and Offset to grab one chunk of data at a > time. This is, of course, a serious problem for mutli-user performance > since eash user would need their own temp table or view. How come nobody's ever thought of cursors? DECLARE foo CURSOR FOR SELECT stuff FROM stuff WHERE foo ORDER BY something; Hop forward N rows? MOVE FORWARD $n IN foo Want M rows? FETCH FORWARD $m IN foo /Steve