From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Huxton <dev@archonet.com>
Cc: andrew@pillette.com
Cc: pgsql-sql@postgresql.org
Subject: Re: MOVE in SQL vs PLPGSQL
Date: Wed, 05 Oct 2005 11:43:04 -0400
Message-ID: <19176.1128526984@sss.pgh.pa.us> (raw)
In-Reply-To: <4343EABB.6030808@archonet.com>
References: <200510051417.j95EH0518161@pillette.com>
<4343EABB.6030808@archonet.com>
Richard Huxton <dev@archonet.com> writes:
> Ah, now I see what you're saying. You're quite right in your suspicions,
> "MOVE..." isn't supported for plpgsql cursors. You could probably do
> something with EXECUTE and returning a refcursor from a previous
> function, but that sounds fiddly.
> I must admit, on the odd occasion I want to skip a row, I just FETCH it
> and move on. Anyone else?
There is something on the TODO list about improving plpgsql's cursor
functionality --- there's no reason it shouldn't have MOVE, except that
no one got around to it yet.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, dev@archonet.com, andrew@pillette.com
Subject: Re: MOVE in SQL vs PLPGSQL
In-Reply-To: <19176.1128526984@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox