Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2137370996.1132739257225.JavaMail.jira@ajax.apache.org>
Date: Wed, 23 Nov 2005 10:47:37 +0100 (CET)
From: "Fernanda Pizzorno (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-718) Network client: deleteRow() makes getter
 methods return nulls for the following rows.
In-Reply-To: <1537691637.1132330961663.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Fernanda Pizzorno updated DERBY-718:
------------------------------------

    Attachment: DERBY-718.diff
                DERBY-718.stat

The problem was caused by isUpdateDeleteHole being set to true after a deleteRow operation but not being set back to false after moving out of the hole. This patch sets isUpdateDeleteHole to false when moving to the next row and adds tests for it in lang/updatableResultSet.java.

I have run successfully run derbyall.

Can someone please review this patch?

> 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