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

From Bruce Momjian
Subject Re: MOVE LAST: why?
Date
Msg-id 200301130048.h0D0m2O27520@candle.pha.pa.us
Whole thread Raw
In response to Re: MOVE LAST: why?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> 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.

OK.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: MOVE LAST: why?
Next
From: Kevin Brown
Date:
Subject: Re: Prepared statements question