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

From Hiroshi Inoue
Subject Re: MOVE LAST: why?
Date
Msg-id 3E21FC5A.5FEE7FFC@tpf.co.jp
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>)
List pgsql-hackers
Bruce Momjian wrote:
> 
> Hiroshi Inoue wrote:
> > > Honestly I'm not so enthusiastic about scrollable cursors.
> > > Even though PostgreSQL provides an efficient scrollable
> > > cursor, I would use it little unless it could survive
> > > across transactions.
> > >
> > > Anyway it's too bad that FETCH LAST means FETCH ALL.
> >
> > I would remove LAST, RELATIVE and SCROLL keywords
> > for cursor related operations if there's no objection.
> 
> 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.

regards,
Hiroshi Inouehttp://w2422.nsk.ne.jp/~inoue/


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: SQL flagger
Next
From: Bruce Momjian
Date:
Subject: Re: MOVE LAST: why?