From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: MOVE LAST: why? |
Date: | 2003-01-13 00:44:50 |
Message-ID: | 16921.1042418690@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-01-13 00:48:02 | Re: MOVE LAST: why? |
Previous Message | Bruce Momjian | 2003-01-12 23:57:12 | Re: MOVE LAST: why? |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-01-13 00:48:02 | Re: MOVE LAST: why? |
Previous Message | Bruce Momjian | 2003-01-12 23:57:12 | Re: MOVE LAST: why? |