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:51:16 |
Message-ID: | 20001115125116.A25885@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:
> Stephen,
>
> > 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
>
> I'm intrigued by this. How would I retrieve cursor rows into a web
> application? If we could output a cursor to a functon result (we
> can't), it would be easy, but I'm not sure otherwise.
The result of the FETCH is something you can use pg_fetch_* functions
on as usual.
From | Date | Subject | |
---|---|---|---|
Next Message | chriswood | 2000-11-28 17:26:06 | Question re large objects |
Previous Message | Josh Berkus | 2000-11-15 17:31:38 | Re: Re: [SQL] FTI, paged, ranked searching and efficiency. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-11-15 18:19:45 | Re: Index problem |
Previous Message | Josh Berkus | 2000-11-15 17:31:38 | Re: Re: [SQL] FTI, paged, ranked searching and efficiency. |