pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Hiroshi Inoue <Inoue@tpf.co.jp>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: MOVE LAST: why?
Date: Thu, 09 Jan 2003 08:53:50 +0900
Message-ID: <3E1CBA0E.8232CF23@tpf.co.jp> (raw)
References: <200301072329.h07NT2X28922@candle.pha.pa.us>
	<27934.1041984327@sss.pgh.pa.us>
	<3E1B9DCD.75859501@tpf.co.jp>
	<501.1041997832@sss.pgh.pa.us>
	<3E1BA5E6.9463718F@tpf.co.jp>
	<863.1042000401@sss.pgh.pa.us>
	<3E1BAFF6.B0114A67@tpf.co.jp>
	<1082.1042002375@sss.pgh.pa.us>
	<3E1BEFFE.88B57516@tpf.co.jp>
	<22435.1042065746@sss.pgh.pa.us>
	<22682.1042067111@sss.pgh.pa.us>

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/



view thread (25+ messages)  latest in thread

Message-ID: <3E1CBA0E.8232CF23@tpf.co.jp>
Permalink:  ../3E1CBA0E.8232CF23@tpf.co.jp/
Also on:    postgresql.org/message-id/3E1CBA0E.8232CF23@tpf.co.jp

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: Inoue@tpf.co.jp, tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, pgsql-hackers@postgresql.org
  Subject: Re: MOVE LAST: why?
  In-Reply-To: <3E1CBA0E.8232CF23@tpf.co.jp>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox