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/18 17:22:41 UTC
[jira] Created: (DERBY-718) Network client: deleteRow() makes getter methods return nulls for the following rows.
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
Assigned to: Fernanda Pizzorno
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
Re: [jira] Updated: (DERBY-718) Network client: deleteRow() makes
getter methods return nulls for the following rows.
Posted by "Bernt M. Johnsen" <Be...@Sun.COM>.
Reviewed and committed.
>>>>>>>>>>>> Fernanda Pizzorno (JIRA) wrote (2005-11-23 14:44:36):
> [ http://issues.apache.org/jira/browse/DERBY-718?page=all ]
>
> Fernanda Pizzorno updated DERBY-718:
> ------------------------------------
>
> Attachment: DERBY-718.diff
> DERBY-718.stat
>
> > 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
>
--
Bernt Marius Johnsen, Database Technology Group,
Sun Microsystems, Trondheim, Norway
[jira] Updated: (DERBY-718) Network client: deleteRow() makes getter methods return nulls for the following rows.
Posted by "Fernanda Pizzorno (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-718?page=all ]
Fernanda Pizzorno updated DERBY-718:
------------------------------------
Attachment: (was: DERBY-718.diff)
> 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: 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
[jira] Resolved: (DERBY-718) Network client: deleteRow() makes getter methods return nulls for the following rows.
Posted by "Bernt M. Johnsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-718?page=all ]
Bernt M. Johnsen resolved DERBY-718:
------------------------------------
Resolution: Fixed
> 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
[jira] Closed: (DERBY-718) Network client: deleteRow() makes getter methods return nulls for the following rows.
Posted by "Fernanda Pizzorno (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-718) Network client: deleteRow() makes getter methods return nulls for the following rows.
Posted by "Fernanda Pizzorno (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-718?page=all ]
Fernanda Pizzorno updated DERBY-718:
------------------------------------
Attachment: (was: DERBY-718.stat)
> 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: 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
[jira] Updated: (DERBY-718) Network client: deleteRow() makes getter methods return nulls for the following rows.
Posted by "Fernanda Pizzorno (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-718?page=all ]
Fernanda Pizzorno updated DERBY-718:
------------------------------------
Attachment: testDeleteRow.java
> 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: 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
[jira] Updated: (DERBY-718) Network client: deleteRow() makes
getter methods return nulls for the following rows.
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-718?page=all ]
Kathey Marsden updated DERBY-718:
---------------------------------
Fix Version: 10.2.0.0
Version: 10.2.0.0
set affects and fix version to 10.2
> 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
> Versions: 10.2.0.0
> Reporter: Fernanda Pizzorno
> Assignee: Fernanda Pizzorno
> Fix For: 10.2.0.0
> 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
[jira] Updated: (DERBY-718) Network client: deleteRow() makes getter methods return nulls for the following rows.
Posted by "Fernanda Pizzorno (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-718) Network client: deleteRow() makes getter methods return nulls for the following rows.
Posted by "Fernanda Pizzorno (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-718?page=all ]
Fernanda Pizzorno updated DERBY-718:
------------------------------------
Attachment: DERBY-718.diff
DERBY-718.stat
> 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