From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
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> (raw)
> 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
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: tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, pgsql-hackers@postgreSQL.org
Subject: Re: MOVE LAST: why?
In-Reply-To: <27476.1041980838@sss.pgh.pa.us>
* 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