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

From Hiroshi Inoue
Subject Re: MOVE LAST: why?
Date
Msg-id 3E1BAFF6.B0114A67@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?
List pgsql-hackers
Tom Lane wrote:
> 
> Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> > Tom Lane wrote:
> >> Sure.  FETCH n in Postgres has always corresponded to FETCH RELATIVE n.
> 
> > IIRC in SQL standard FETCH retrieves rows one by one.
> 
> Yes, Postgres' idea of FETCH is only weakly related to the spec's idea.
> But I believe you get similar results if you consider only the row last
> returned by our FETCH.

FETCH n is a PostgreSQL's extention to retrieve multiple
rows by one FETCH not related to FETCH RELATIVE at all.

FETCH LAST should return the last one row.
FETCH RELATIVE m should return a row after skipping
m rows if we follow the SQL standard and so the current
implementation of FETCH RELATIVE is broken.

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


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: MOVE LAST: why?
Next
From: Tom Lane
Date:
Subject: Re: redo error?