Tom Lane <[EMAIL PROTECTED]> writes:
> Richard Huxton 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,
Richard Huxton 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
[EMAIL PROTECTED] wrote:
Andrew - your question doesn't seem to make sense - can you give
some more details? Are you having some problem with cursors in
plpgsql?
Yes. I'd like the effect of the plain SQL MOVE with a PLPGSQL cursor.
I'm writing a procedure for which SQL is inadequate (I need
co
[EMAIL PROTECTED] wrote:
I can't find a good way to skip over a large number of records in
PLPGSQL (I want to fast-forward and I don't need the I/O of reading
and throwing away hundreds of records.) In SQL, I could just use
MOVE. That doesn't appear to be supported in PLPGSQL?! Help?
Andrew - y
I can't find a good way to skip over a large number of records in PLPGSQL (I
want to fast-forward and I don't need the I/O of reading and throwing away
hundreds of records.) In SQL, I could just use MOVE. That doesn't appear to be
supported in PLPGSQL?! Help?
---(end of
