Re: For cursors, there is FETCH and MOVE, why no TELL?

From: Hakan Kocaman <hkocam(at)gmail(dot)com>
To: Marc Balmer <marc(at)msys(dot)ch>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: For cursors, there is FETCH and MOVE, why no TELL?
Date: 2015-02-09 12:13:00
Message-ID: CAKoGa8+eu3JnVsuQSceebv7wTF-8NBaQ2DUdS+99r=ZfQJtKYg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

2015-02-09 10:37 GMT+01:00 Marc Balmer <marc(at)msys(dot)ch>:

>
> (I use cursors to display large datasets in a page-wise way, where the
> user can move per-page, or, when displaying a single record, per record.
> When the user goes back from per-record view to page-view, I have to
> restore the cursor to the position it was on before the user changed to
> per-record view.)
>
>
> On a totaly unrelated note:
http://use-the-index-luke.com/de/blog/2013-07/pagination-done-the-postgresql-way

kind regards
hakm kocaman

> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Abhijit Menon-Sen 2015-02-09 13:20:46 Re: What exactly is our CRC algorithm?
Previous Message Michael Paquier 2015-02-09 12:02:35 Re: The return value of allocate_recordbuf()