Re: FETCH FORWARD 0 and "cursor can only scan forward" error - Mailing list pgsql-general

From Trigve Siver
Subject Re: FETCH FORWARD 0 and "cursor can only scan forward" error
Date
Msg-id 1378314614.11579.YahooMailNeo@web125706.mail.ne1.yahoo.com
Whole thread Raw
In response to Re: FETCH FORWARD 0 and "cursor can only scan forward" error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general

> From: Tom Lane <tgl@sss.pgh.pa.us>

> To: Trigve Siver <trigves@yahoo.com>
> Cc: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
> Sent: Wednesday, September 4, 2013 7:04 PM
> Subject: Re: [GENERAL] FETCH FORWARD 0 and "cursor can only scan forward" error
>
>T rigve Siver <trigves@yahoo.com> writes:
>>  yes I know that when specifying "FORWARD 0" that no move is done
> and
>>  actual record is returned. But my question is why it is forbidden by
> "NO
>>  SCROLL"?
>
> Because it's implemented as "back up 1 row and re-fetch".

Thanks,
So I'll try to emulate it somehow then.
 
>             regards, tom lane
>

Trigve


pgsql-general by date:

Previous
From: Evan Martin
Date:
Subject: Re: Spurious error messages from pg_restore
Next
From: Raphael Araújo e Silva
Date:
Subject: pg_catalog question: Sequence attributes.