Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 44399 invoked from network); 2 Mar 2006 13:19:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Mar 2006 13:19:24 -0000 Received: (qmail 93816 invoked by uid 500); 2 Mar 2006 13:20:06 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 93580 invoked by uid 500); 2 Mar 2006 13:20:05 -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 93569 invoked by uid 99); 2 Mar 2006 13:20:05 -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; Thu, 02 Mar 2006 05:20:03 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 21BF1DE for ; Thu, 2 Mar 2006 14:19:42 +0100 (CET) Message-ID: <1750468572.1141305582136.JavaMail.jira@ajax.apache.org> Date: Thu, 2 Mar 2006 14:19:42 +0100 (CET) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-948) Miscellaneous ResultSet methods added by JDBC 4 In-Reply-To: <2142502737.1139608040728.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-948?page=all ] Knut Anders Hatlen updated DERBY-948: ------------------------------------- Attachment: DERBY-948-v3.diff DERBY-948-v3.stat I investigated the possibility for null pointer exceptions further. The only result sets that return null in getStatement() are those created by getNewRowSet() and getOldRowSet() in InternalTriggerExecutionContext. Those result sets are not exposed to JDBC applications, so applications can't call getHoldability() on them anyway. However, I updated the patch with a comment about the null case, and made getHoldability() return CLOSE_CURSORS_AT_COMMIT instead of throwing NullPointerException. > Miscellaneous ResultSet methods added by JDBC 4 > ----------------------------------------------- > > Key: DERBY-948 > URL: http://issues.apache.org/jira/browse/DERBY-948 > Project: Derby > Type: New Feature > Components: JDBC > Reporter: Rick Hillegas > Assignee: Knut Anders Hatlen > Fix For: 10.2.0.0 > Attachments: DERBY-948-v1.diff, DERBY-948-v1.stat, DERBY-948-v2.diff, DERBY-948-v2.stat, DERBY-948-v3.diff, DERBY-948-v3.stat > > As described in the JDBC 4 spec sections 16 and 3.1. > This provides support for new ResultSet methods added by JDBC4 and not addressed by other JIRAs: getHoldability() and isClosed(). -- 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