db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DERBY-4843) Consult isPoolable hint before caching prepared statement
Date Mon, 06 Jun 2011 10:53:59 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan closed DERBY-4843.
----------------------------------


Closing issue.

> 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
>             Fix For: 10.7.1.1
>
>         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

Mime
View raw message