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-08 23:53:50
Message-ID: 3E1CBA0E.8232CF23@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

Tom Lane wrote:
>
> Perhaps we could do something with a hybrid technique: don't materialize
> the cursor output unless user actually asks for backwards scan.

Or we can check the existence of SCROLL keyword which is
currently ignored. In the first place SQL standard only
allows NEXT fetch unless SCROLL is specified.

regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2003-01-09 00:00:34 Re: MOVE LAST: why?
Previous Message Tom Lane 2003-01-08 23:05:11 Re: MOVE LAST: why?

Browse pgsql-interfaces by date

  From Date Subject
Next Message Hannu Krosing 2003-01-09 00:00:34 Re: MOVE LAST: why?
Previous Message Tom Lane 2003-01-08 23:05:11 Re: MOVE LAST: why?