Re: Re: [SQL] FTI, paged, ranked searching and efficiency.

From: Stephen van Egmond <svanegmond(at)bang(dot)dhs(dot)org>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: sqllist <pgsql-sql(at)postgresql(dot)org>, phpp <pgsql-php(at)postgresql(dot)org>
Subject: Re: Re: [SQL] FTI, paged, ranked searching and efficiency.
Date: 2000-11-15 17:25:16
Message-ID: 20001115122516.B25685@bang.dhs.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-php pgsql-sql

Josh Berkus (josh(at)agliodbs(dot)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

In response to

Responses

Browse pgsql-php by date

  From Date Subject
Next Message Stephen van Egmond 2000-11-15 17:28:48 Re: Re: [SQL] FTI, paged, ranked searching and efficiency.
Previous Message Josh Berkus 2000-11-15 17:03:22 Re: [SQL] FTI, paged, ranked searching and efficiency.

Browse pgsql-sql by date

  From Date Subject
Next Message Stephen van Egmond 2000-11-15 17:28:48 Re: Re: [SQL] FTI, paged, ranked searching and efficiency.
Previous Message Josh Berkus 2000-11-15 17:03:22 Re: [SQL] FTI, paged, ranked searching and efficiency.