Re: cursors: SCROLL default, error messages

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: cursors: SCROLL default, error messages
Date: 2003-03-21 17:33:28
Message-ID: 13982.1048268008@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Neil Conway <neilc(at)samurai(dot)com> writes:
> On Fri, 2003-03-21 at 12:12, Tom Lane wrote:
>> (No problem here with adding the noise-word option, of course.)

> Note that it won't be a noise word: if NO SCROLL is specified, an
> attempt to do a backward fetch on a non-scrollable cursor will yield an
> error.

Hm. We could imagine a three-way option:
NO SCROLL always error if fetch backwards
<nothing> allow if plan supports it
SCROLL allow, add overhead if needed to support
The <nothing> case would deviate from the spec but would give backwards
compatibility.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-03-21 17:42:25 Re: [INTERFACES] Roadmap for FE/BE protocol redesign
Previous Message Neil Conway 2003-03-21 17:29:42 Re: cursors: SCROLL default, error messages