Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 10582 invoked from network); 22 Nov 2005 00:55:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Nov 2005 00:55:05 -0000 Received: (qmail 89404 invoked by uid 500); 22 Nov 2005 00:55:04 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 89384 invoked by uid 500); 22 Nov 2005 00:55:04 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 89375 invoked by uid 99); 22 Nov 2005 00:55:04 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Nov 2005 16:55:02 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id CCD98591 for ; Tue, 22 Nov 2005 01:54:41 +0100 (CET) Message-ID: <875117272.1132620881836.JavaMail.jira@ajax.apache.org> Date: Tue, 22 Nov 2005 01:54:41 +0100 (CET) From: "Dag H. Wanvik (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-722) updateRow invalidates current row in result set Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N updateRow invalidates current row in result set ----------------------------------------------- Key: DERBY-722 URL: http://issues.apache.org/jira/browse/DERBY-722 Project: Derby Type: Bug Components: Network Client, JDBC Versions: 10.1.2.2, 10.1.3.0, 10.2.0.0, 10.1.2.1, 10.1.2.0, 10.1.1.2, 10.1.1.1, 10.1.1.0 Environment: Sun JDK 1.4.2, Solaris 10 Reporter: Dag H. Wanvik Priority: Minor In both the network and embedded drivers, after an updateRow has been performed, reading the current row fails. A new next() is required to get a new valid position, as shown by the attached repro. In contrast to the case for deleteRow, JDBC does not require a repositioning after an updateRow. -- 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