The following bug has been logged online:
Bug reference: 1121
Logged by: Bob Messenger
Email address: [EMAIL PROTECTED]
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
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
