Re: actualised forgotten Magnus's patch for plpgsql MOVE statement - Mailing list pgsql-patches

From Neil Conway
Subject Re: actualised forgotten Magnus's patch for plpgsql MOVE statement
Date
Msg-id 1177810052.6440.196.camel@localhost.localdomain
Whole thread Raw
In response to actualised forgotten Magnus's patch for plpgsql MOVE statement  ("Pavel Stehule" <pavel.stehule@hotmail.com>)
Responses Re: actualised forgotten Magnus's patch for plpgsql MOVE statement  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
On Fri, 2007-04-20 at 09:46 +0200, Pavel Stehule wrote:
> I refreshed Magnus's patch
> http://archives.postgresql.org/pgsql-patches/2007-02/msg00275.php from
> februar.

Applied, thanks.

BTW, I notice that the documentation for PL/PgSQL's FETCH command states
that only the direction variants that fetch a *single* row are allowed.
This is not actually the case: FETCH RELATIVE 2 FROM c INTO v results in
assigning the first row from "c" into "v", and then discarding the
second row. Is this the best behavior? At the least, we should describe
it in the documentation.

> p.s. scrollable cursors in plpgsql need little work still. I forgot for
> nonstandard (postgresql extension) direction forward all, forward n,
> backward n. Forward all propably hasn't sense.

Yes, these are certainly needed for MOVE, and we may as well allow them
for FETCH as well.

-Neil



pgsql-patches by date:

Previous
From: Neil Conway
Date:
Subject: Re: Hash function for numeric (WIP)
Next
From: Tom Lane
Date:
Subject: Re: actualised forgotten Magnus's patch for plpgsql MOVE statement