Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 12141 invoked from network); 29 Jan 2008 09:24:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Jan 2008 09:24:57 -0000 Received: (qmail 48470 invoked by uid 500); 29 Jan 2008 09:24:48 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 48412 invoked by uid 500); 29 Jan 2008 09:24:48 -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 48403 invoked by uid 99); 29 Jan 2008 09:24:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jan 2008 01:24:48 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jan 2008 09:24:41 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 150E87141FE for ; Tue, 29 Jan 2008 01:24:34 -0800 (PST) Message-ID: <8539584.1201598674083.JavaMail.jira@brutus> Date: Tue, 29 Jan 2008 01:24:34 -0800 (PST) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-3324) JDBC statement cache implementation In-Reply-To: <21071357.1200589298857.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3324: ----------------------------------- Attachment: derby-3324-1d-jdbc_statementcache.diff 'derby-3324-1d-jdbc_statementcache.diff' deprecates version 1c and contains only two changes. I removed the redundant null check Knut Anders commented on and fixed some bad formatting in the string created by StatementKey.toString. > JDBC statement cache implementation > ----------------------------------- > > Key: DERBY-3324 > URL: https://issues.apache.org/jira/browse/DERBY-3324 > Project: Derby > Issue Type: Sub-task > Components: Network Client > Affects Versions: 10.4.0.0 > Reporter: Kristian Waagan > Assignee: Kristian Waagan > Priority: Minor > Fix For: 10.4.0.0 > > Attachments: derby-3324-1a-jdbc_statementcache.diff, derby-3324-1a-jdbc_statementcache.stat, derby-3324-1b-jdbc_statementcache.diff, derby-3324-1b-jdbc_statementcache.stat, derby-3324-1c-jdbc_statementcache.diff, derby-3324-1c-jdbc_statementcache.stat, derby-3324-1d-jdbc_statementcache.diff > > > Implement a cache for storing JDBC prepared statement objects. > The cache will be responsible for holding free prepared statement objects that can be reused, and also to throw away objects if the cache grows too big. > All objects in the cache must belong to the same physical connection, but they can be reused across logical connections obtained from a single physical connection in a connection pool. > This component is probably a candidate for code sharing between the client and the embedded driver. Sharing will not be part of this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.