You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2011/05/25 14:53:51 UTC
[jira] [Updated] (DERBY-4843) Consult isPoolable hint before
caching prepared statement
[ https://issues.apache.org/jira/browse/DERBY-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-4843:
-----------------------------------
Attachment: derby-4843-2a-test_isPoolable.diff
Attaching patch 2a, which tests that the isPoolable-hint is consulted when running with the JDBC client side statement cache enabled.
I verified that cpTestIsPoolableHintFalse failed without the code fix (patch 1b).
Patch ready for review.
> 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.1.1
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Trivial
> Attachments: derby-4843-1a-consult_isPoolable.diff, derby-4843-1b-consult_isPoolable.diff, derby-4843-2a-test_isPoolable.diff
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira