Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 80023 invoked from network); 6 Apr 2006 18:12:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Apr 2006 18:12:58 -0000 Received: (qmail 75079 invoked by uid 500); 6 Apr 2006 18:12:57 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 74851 invoked by uid 500); 6 Apr 2006 18:12:56 -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 74842 invoked by uid 99); 6 Apr 2006 18:12:56 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Apr 2006 11:12:56 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= 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; Thu, 06 Apr 2006 11:12:56 -0700 Received: from ajax (localhost.localdomain [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 59EE3D4A02 for ; Thu, 6 Apr 2006 19:12:35 +0100 (BST) Message-ID: <1743007301.1144347155357.JavaMail.jira@ajax> Date: Thu, 6 Apr 2006 19:12:35 +0100 (BST) From: "Daniel John Debrunner (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Closed: (DERBY-1101) ResultSet.getHoldabilty will return incorrect value when the ResultSet is obtained from a procedure call In-Reply-To: <453076411.1142195693839.JavaMail.jira@ajax> 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-1101?page=all ] Daniel John Debrunner closed DERBY-1101: ---------------------------------------- Closed - Actually I only realised once I was adding the contribution line in the commit message that this was a patch provided by a committer. For some reason I thought it was someone else. Since I'd got so far I thought I might as well continue. :-) > ResultSet.getHoldabilty will return incorrect value when the ResultSet is obtained from a procedure call > -------------------------------------------------------------------------------------------------------- > > Key: DERBY-1101 > URL: http://issues.apache.org/jira/browse/DERBY-1101 > Project: Derby > Type: Bug > Components: JDBC > Versions: 10.2.0.0 > Reporter: Daniel John Debrunner > Assignee: Knut Anders Hatlen > Priority: Minor > Fix For: 10.2.0.0 > Attachments: derby-1101-testcase-v1.diff, derby-1101-v1.diff, derby-1101-v1.stat, testderby1101.java > > EmbedResultSet40.getHoldability returns the holdability of the statement returned by ResultSet.getStatement(). > When a ResultSet is created by a procedure call, its holdability may not match the holdability of the Statement that called the procedure, which is probably what ResultSet.getStatement() should return. > This may not be exposed as a bug yet, but I think this method should be directly obtaining the holdability of the ResultSet using the Activation.getResultSetHoldability() method, rather than through a Statement. Seems a safer approach. -- 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