Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 01B0F476C10 for ; Tue, 7 Jan 2003 18:07:21 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 3E2F4476C00 for ; Tue, 7 Jan 2003 18:07:20 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h07N7I0U027477; Tue, 7 Jan 2003 18:07:18 -0500 (EST) To: Bruce Momjian Cc: pgsql-hackers@postgreSQL.org Subject: MOVE LAST: why? Date: Tue, 07 Jan 2003 18:07:18 -0500 Message-ID: <27476.1041980838@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/357 X-Sequence-Number: 33967 > 2002-11-12 19:44 momjian > > * doc/src/sgml/ref/move.sgml, src/backend/commands/portalcmds.c, > src/backend/executor/execMain.c, src/backend/parser/gram.y, > src/backend/parser/keywords.c, src/backend/tcop/utility.c, > src/include/commands/portalcmds.h, src/include/nodes/parsenodes.h: > Make MOVE/FETCH 0 actually move/fetch 0. Add MOVE LAST to move to > end of cursor. Refresh my memory: what is the point of inventing an additional LAST keyword, when the behavior is exactly the same as MOVE ALL ? regards, tom lane