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

From: Marc Balmer <marc(at)msys(dot)ch>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: For cursors, there is FETCH and MOVE, why no TELL?
Date: 2015-02-09 09:37:58
Message-ID: 54D87FF6.302@msys.ch
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Currently there are FETCH and the (non standard) MOVE commands to work
on cursors.

(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.)

I have to "manually" keep track of the cursor position, but in some
cases it would definitely be easier to just query the current cursor
position directly from the database and later use "MOVE ABSOLUTE" to
rewind it to that position. That could be achieved e.g. by a
hypothetical "TELL <cursor-name>" command. It does, however, not exist
and I have not found an alternative. Is there a way to query the
current cusros position at all? If not, does a TELL command sound like
a good or bad idea?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2015-02-09 09:46:28 Re: For cursors, there is FETCH and MOVE, why no TELL?
Previous Message Jeff Davis 2015-02-09 08:12:29 Re: 9.6 Feature help requested: Inclusion Constraints