| From: | Trigve Siver <trigves(at)yahoo(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: FETCH FORWARD 0 and "cursor can only scan forward" error |
| Date: | 2013-09-04 17:10:14 |
| Message-ID: | 1378314614.11579.YahooMailNeo@web125706.mail.ne1.yahoo.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> To: Trigve Siver <trigves(at)yahoo(dot)com>
> Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)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(at)yahoo(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raphael Araújo e Silva | 2013-09-04 18:33:58 | pg_catalog question: Sequence attributes. |
| Previous Message | Evan Martin | 2013-09-04 17:08:06 | Re: Spurious error messages from pg_restore |