Re: MOVE LAST: why?

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: MOVE LAST: why?
Date: 2003-01-12 16:12:19
Message-ID: EKEJJICOHDIEMGPNIFIJKEBGKFAA.Inoue@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

> Honestly I'm not so enthusiastic about scrollable cursors.
> Even though PostgreSQL provides an efficient scrollable
> cursor, I would use it little unless it could survive
> across transactions.
>
> Anyway it's too bad that FETCH LAST means FETCH ALL.

I would remove LAST, RELATIVE and SCROLL keywords
for cursor related operations if there's no objection.

regards,
Hiroshi Inoue

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2003-01-12 16:20:38 Re: default to WITHOUT OIDS?
Previous Message Bruce Momjian 2003-01-12 14:58:16 Re: Roadmap for 7.4

Browse pgsql-interfaces by date

  From Date Subject
Next Message Bruce Momjian 2003-01-12 16:28:09 Re: MOVE LAST: why?
Previous Message Key88 SF 2003-01-10 17:21:59 Re: libpqxx Large Objects