You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Fernanda Pizzorno (JIRA)" <de...@db.apache.org> on 2005/11/25 10:34:56 UTC

[jira] Closed: (DERBY-718) Network client: deleteRow() makes getter methods return nulls for the following rows.

     [ http://issues.apache.org/jira/browse/DERBY-718?page=all ]
     
Fernanda Pizzorno closed DERBY-718:
-----------------------------------


> Network client: deleteRow() makes getter methods return nulls for the following rows.
> -------------------------------------------------------------------------------------
>
>          Key: DERBY-718
>          URL: http://issues.apache.org/jira/browse/DERBY-718
>      Project: Derby
>         Type: Bug
>   Components: Network Client
>     Reporter: Fernanda Pizzorno
>     Assignee: Fernanda Pizzorno
>  Attachments: DERBY-718.diff, DERBY-718.stat, testDeleteRow.java
>
> On the network driver, the ResultSet.deleteRow() method causes the getXXX() methods in the following rows to return null values. It should be possible to use the getXXX methods after positioning the cursor in the next row. It also has this side effect on *other* result sets if these are created with the same prepared statement.
> The repro case is uploaded as an attachment "testDeleteRow.java"
> Output of the report case:
> List all rows
> Row: 1: Testing 1
> Row: 2: Testing 2
> Row: 3: Testing 3
> Row: 4: Testing 4
> Row: 5: Testing 5
> Row: 6: Testing 6
> Row: 7: Testing 7
> Row: 8: Testing 8
> Row: 9: Testing 9
> Row: 10: Testing 10
> List all rows and delete first row
> Row: 1: Testing 1
> Row deleted!
> Row: 0: null
> Row: 0: null
> Row: 0: null
> Row: 0: null
> Row: 0: null
> Row: 0: null
> Row: 0: null
> Row: 0: null
> Row: 0: null
> List all rows
> Row: 2: Testing 2
> Row: 3: Testing 3
> Row: 4: Testing 4
> Row: 5: Testing 5
> Row: 6: Testing 6
> Row: 7: Testing 7
> Row: 8: Testing 8
> Row: 9: Testing 9
> Row: 10: Testing 10

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira