| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Dave Cramer <dave(at)fastcrypt(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: move 0 behaviour |
| Date: | 2002-10-30 18:32:12 |
| Message-ID: | Pine.LNX.4.44.0210301928450.2006-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-jdbc |
Bruce Momjian writes:
> So, that is why MOVE 0 goes to the end of the cursor. One idea would be
> for MOVE 0 to actually move nothing, but jdbc and others need the
> ability to move the end of the cursor, perhaps to then back up a certain
> amount and read from there. Seems MOVE 0 is the logical way to do that.
> (I can't think of another reasonable value).
It would seem more logical and reasonable for MOVE 0 to do nothing and
have some special syntax such as MOVE LAST to move to the end. (MOVE LAST
would actually be consistent with the standard syntax FETCH LAST.)
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Medi Montaseri | 2002-10-30 18:35:59 | Re: Stream data into Postgres via Perl |
| Previous Message | Robert John Shepherd | 2002-10-30 18:28:28 | Problems with a slow query using a simple JOIN |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-10-30 18:36:40 | Re: [HACKERS] Request for supported platforms |
| Previous Message | Peter Eisentraut | 2002-10-30 18:27:57 | Re: float output precision questions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Barry Lind | 2002-10-30 19:15:05 | Re: JDBC Driver & ResultSet.setFetchSize(int rows) |
| Previous Message | Tom Lane | 2002-10-30 18:19:27 | Re: move 0 behaviour |