| Lists: | pgsql-bugs |
|---|
| From: | "PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #1121: JDBC AbstractJdbc2ResultSet.deleteRow() |
| Date: | 2004-03-30 16:02:15 |
| Message-ID: | 20040330160215.CE7E5CF5711@www.postgresql.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 1121
Logged by: Bob Messenger
Email address: bob(at)cassiancapital(dot)com
PostgreSQL version: 7.4
Operating system: Red Hat 9
Description: JDBC AbstractJdbc2ResultSet.deleteRow()
Details:
Against 7.4.2.
Small bug (unless my workaround below is what I'm supposed to do), should be
easy fix. The deleteRow() function doesn't update the 'current_row'
variable. This means that if you call deleteRow() and then call next() to
fill the rowBuffer with information for the next row you actually skip a
row.
I'm working around it at the moment by calling isAfterEnd() and then
moveToCurrentRow() after every deleteRow().
Hope this helps, Bob
| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Bob Messenger <bob(at)cassiancapital(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #1121: JDBC AbstractJdbc2ResultSet.deleteRow() |
| Date: | 2004-06-16 05:14:29 |
| Message-ID: | Pine.BSO.4.56.0406160012440.30439@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-bugs |
On Tue, 30 Mar 2004, PostgreSQL Bugs List wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1121
> Logged by: Bob Messenger
>
> Description: JDBC AbstractJdbc2ResultSet.deleteRow()
>
> Small bug (unless my workaround below is what I'm supposed to do), should be
> easy fix. The deleteRow() function doesn't update the 'current_row'
> variable. This means that if you call deleteRow() and then call next() to
> fill the rowBuffer with information for the next row you actually skip a
> row.
>
This has been fixed in both the 7.4 and 7.5 cvs versions. Sorry for the
delay, I originally thought the problem was more complicated as described
in my response to another complaint of the same issue here:
http://archives.postgresql.org/pgsql-bugs/2004-06/msg00055.php
Kris Jurka