Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 61897 invoked from network); 9 Aug 2006 13:42:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Aug 2006 13:42:00 -0000 Received: (qmail 20052 invoked by uid 500); 9 Aug 2006 13:41:59 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 20011 invoked by uid 500); 9 Aug 2006 13:41:59 -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 20002 invoked by uid 99); 9 Aug 2006 13:41:59 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Aug 2006 06:41:59 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Aug 2006 06:41:58 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C0B6A7141F2 for ; Wed, 9 Aug 2006 13:39:14 +0000 (GMT) Message-ID: <3010810.1155130754787.JavaMail.jira@brutus> Date: Wed, 9 Aug 2006 06:39:14 -0700 (PDT) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-694) Statement exceptions cause all the connection's result sets to be closed with the client driver In-Reply-To: <828757287.1131539539963.JavaMail.jira@ajax.apache.org> 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 [ http://issues.apache.org/jira/browse/DERBY-694?page=comments#action_12426915 ] Rick Hillegas commented on DERBY-694: ------------------------------------- Thanks for all of this thoughtful work, Narayanan. This improves the situation. Committed at revision 430051. > Statement exceptions cause all the connection's result sets to be closed with the client driver > ----------------------------------------------------------------------------------------------- > > Key: DERBY-694 > URL: http://issues.apache.org/jira/browse/DERBY-694 > Project: Derby > Issue Type: Bug > Components: Network Client > Affects Versions: 10.1.1.1 > Reporter: Oyvind Bakksjo > Assigned To: V.Narayanan > Priority: Minor > Attachments: DERBY-694.html, DERBY-694_upload_v1.diff, DERBY-694_upload_v1.stat, DERBY-694_v2.diff, DERBY-694_v2.stat, DERBY-694_v3.diff, DERBY-694_v3.stat, DERBY-694_v4.diff, DERBY-694_v4.stat, DERBY-694_v5.diff, DERBY-694_v5.stat, DERBY-694_v6.diff, DERBY-694_v6.stat, StatementRollbackTest.java > > > Scenario: > Autocommit off. Have two prepared statements, calling executeQuery() on both, giving me two result sets. Can fetch data from both with next(). If one statement gets an exception (say, caused by a division by zero), not only this statement's result set is closed, but also the other open resultset. This happens with the client driver, whereas in embedded mode, the other result set is unaffected by the exception in the first result set (as it should be). -- 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