Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <5551716.111911286972192518.JavaMail.jira@thor>
Date: Wed, 13 Oct 2010 08:16:32 -0400 (EDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4843) Consult isPoolable hint before
 caching prepared statement
In-Reply-To: <4895038.111541286970633247.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920510#action_12920510 ] 

Knut Anders Hatlen commented on DERBY-4843:
-------------------------------------------

Prepared statements are initialized with poolable == true, right? In that case it sounds reasonable to skip statements that have the hint set to false, since that means the user has explicitly called setPoolable(false).

> Consult isPoolable hint before caching prepared statement
> ---------------------------------------------------------
>
>                 Key: DERBY-4843
>                 URL: https://issues.apache.org/jira/browse/DERBY-4843
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Client
>    Affects Versions: 10.4.2.0, 10.5.3.0, 10.6.2.1, 10.7.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Trivial
>
> The Derby  JDBC client side statement cache should consult the value of the isPoolable hint before caching prepared statements.
> This will give users the ability to avoid that short-lived prepared statements push out more frequently used prepared statements in the case of a full statement cache.
> The API JavaDoc says that it is up to the cache whether the hint is used or not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.