Re: MOVE LAST: why?
От | Hiroshi Inoue |
---|---|
Тема | Re: MOVE LAST: why? |
Дата | |
Msg-id | 3E1BAFF6.B0114A67@tpf.co.jp обсуждение исходный текст |
Ответ на | Re: MOVE LAST: why? (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: MOVE LAST: why?
|
Список | 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 по дате отправления: