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
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.
In response to
pgsql-patches by date
|Next:||From: Tom Lane||Date: 2007-04-29 03:37:41|
|Subject: Re: actualised forgotten Magnus's patch for plpgsql MOVE statement |
|Previous:||From: Neil Conway||Date: 2007-04-28 22:47:10|
|Subject: Re: Hash function for numeric (WIP)|