From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Postgres User <postgres(dot)developer(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] Fun with Cursors- how to rewind a cursor |
Date: | 2007-03-25 01:51:32 |
Message-ID: | 200703250151.l2P1pWl07285@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Tom Lane wrote:
> "Postgres User" <postgres(dot)developer(at)gmail(dot)com> writes:
> > On 3/1/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> "Postgres User" <postgres(dot)developer(at)gmail(dot)com> writes:
> >>> <before opening cursor> ref_entry = 'c_entry';
> >>> <after looping thru cursor> MOVE Backward All In c_entry;
> >>
> >> You have to use EXECUTE for the latter.
>
> > I had tried several variations of MOVE Backward inside an Execute
> > statement earlier. And now, I'm seeing this error appear again:
> > ERROR: 0A000: cannot manipulate cursors directly in PL/pgSQL
>
> Hm, you're right. This arises from the fact that _SPI_execute_plan
> rejects cursor-related utility statements. While I'd never stopped
> to question that before, it does seem like this restriction is a
> bit pointless. Does anyone remember why it's like that?
Is there anything to do on this item?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-03-25 02:21:40 | Re: Why can't I put a BEFORE EACH ROW trigger on a view? |
Previous Message | Bruce Momjian | 2007-03-25 01:51:07 | Re: Configure can't find com_err on OpenBSD for --with-krb5 |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2007-03-25 01:58:33 | Re: BSD advertizing clause in some files |
Previous Message | Bruce Momjian | 2007-03-25 01:44:47 | Re: Optimized pgbench for 8.3 |