Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 5A3C5475EE1 for ; Sun, 12 Jan 2003 11:10:10 -0500 (EST) Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34]) by postgresql.org (Postfix) with SMTP id 0C441475E71 for ; Sun, 12 Jan 2003 11:10:09 -0500 (EST) Received: (qmail 5825 invoked from network); 12 Jan 2003 16:10:12 -0000 X-Authentication: inoue was authenticated by sd.tpf.co.jp at 12 Jan 2003 16:10:12 -0000 Received: from unknown (HELO mcadnote1) (219.61.40.16) by sd.tpf.co.jp with SMTP; 12 Jan 2003 16:10:12 -0000 From: "Hiroshi Inoue" To: "Tom Lane" Cc: "Bruce Momjian" , Subject: Re: MOVE LAST: why? Date: Mon, 13 Jan 2003 01:12:19 +0900 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3E1CEA18.18E921A0@tpf.co.jp> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/529 X-Sequence-Number: 34139 > 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