Re: MOVE LAST: why? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: MOVE LAST: why?
Date
Msg-id 16921.1042418690@sss.pgh.pa.us
Whole thread Raw
In response to Re: MOVE LAST: why?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: MOVE LAST: why?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: MOVE LAST: why?  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Hiroshi Inoue wrote:
> Are you suggesting removing FETCH LAST _and_ MOVE LAST?. 
>> 
>> Yes. Should cursors be positioned on the last row
>> or EOF by MOVE LAST ? Anyway I see no necessity to use
>> the standard keyword LAST currently.
>> 
> I think MOVE LAST works well.

> OK, so we will switch it to MOVE END.  That seems OK.

What is good about that???  We already have a nonstandard keyword
for this functionality: MOVE ALL.  There is no reason to invent another
one.

I tend to agree with Hiroshi that it's a bad idea to add a standard
keyword to represent not-quite-standard behavior.  MOVE ALL is our
historical spelling for this functionality, and adding MOVE LAST is
not really bringing anything to the party.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: MOVE LAST: why?
Next
From: Bruce Momjian
Date:
Subject: Re: MOVE LAST: why?