Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 89143 invoked from network); 30 Apr 2009 21:03:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Apr 2009 21:03:53 -0000 Received: (qmail 16767 invoked by uid 500); 30 Apr 2009 21:03:53 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 16710 invoked by uid 500); 30 Apr 2009 21:03:53 -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 16701 invoked by uid 99); 30 Apr 2009 21:03:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Apr 2009 21:03:53 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Apr 2009 21:03:51 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4F027234C003 for ; Thu, 30 Apr 2009 14:03:30 -0700 (PDT) Message-ID: <245892468.1241125410309.JavaMail.jira@brutus> Date: Thu, 30 Apr 2009 14:03:30 -0700 (PDT) From: "Tiago R. Espinha (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-3839) Convert "org.apache.derbyTesting.functionTests.tests.store.holdCursorJDBC30.sql" to junit. In-Reply-To: <2099681545.1218704144316.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tiago R. Espinha updated DERBY-3839: ------------------------------------ Attachment: ReproHoldCursorBug.java I have run into what seems to be another bug. Initially I thought this could simply be a normal different behaviour between embedded and client drivers. Kathey has however suggested that it could be a bug so I'm posting it here to get some opinions. The issue is on the embedded driver. The problem happens when we create a cursor and while having it on a certain record, another statement is executed that deletes both the record that the cursor is on and the next one. If afterwards we advance the cursor, the embedded driver will act as if the rows haven't been deleted at all, whereas the client driver seems to behave correctly. It needs to be said though that the client driver will only pass as long as the bulkFetchDefault is set to 1. Any other values on this property seem to make the client error out as well. > Convert "org.apache.derbyTesting.functionTests.tests.store.holdCursorJDBC30.sql" to junit. > ------------------------------------------------------------------------------------------- > > Key: DERBY-3839 > URL: https://issues.apache.org/jira/browse/DERBY-3839 > Project: Derby > Issue Type: Test > Components: Test > Reporter: Junjie Peng > Assignee: Tiago R. Espinha > Attachments: derby-3839-1.patch, derby-3839-1.stat, derby-3839.patch, ReproHoldCursorBug.java, ReproHoldCursorBug.java, ReproHoldCursorBug.java > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.