| 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: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | MOVE LAST: why? |
| Date: | 2003-01-07 23:07:18 |
| Message-ID: | 27476.1041980838@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
> 2002-11-12 19:44 momjian
>
> * doc/src/sgml/ref/move.sgml, src/backend/commands/portalcmds.c,
> src/backend/executor/execMain.c, src/backend/parser/gram.y,
> src/backend/parser/keywords.c, src/backend/tcop/utility.c,
> src/include/commands/portalcmds.h, src/include/nodes/parsenodes.h:
> Make MOVE/FETCH 0 actually move/fetch 0. Add MOVE LAST to move to
> end of cursor.
Refresh my memory: what is the point of inventing an additional LAST
keyword, when the behavior is exactly the same as MOVE ALL ?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vince Vielhaber | 2003-01-07 23:07:36 | Re: PostgreSQL site, put up or shut up? |
| Previous Message | Dave Page | 2003-01-07 23:05:06 | Re: PostgreSQL site, put up or shut up? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gerhard Häring | 2003-01-07 23:28:53 | Re: [ADMIN] pgdb.py is still wrong in Postgres 7.3.1 rpm |
| Previous Message | Bruce Momjian | 2003-01-07 22:51:43 | Re: [BUGS] pgdb.py is still wrong [not just] in Postgres 7.3.1 |