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] [Resolved] (DERBY-4843) Consult isPoolable hint before caching prepared statement
Date Mon, 30 May 2011 12:20:47 GMT

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

Kristian Waagan resolved DERBY-4843.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.7.1.1

Committed the tests in patch 2a to trunk with revision 1129136.
Back-ports:
  - 10.8: r1129138
  - 10.7: r1129140

I've set the fix version to 10.7.1.1 [1], since that's where the functionality was added.
I don't except more work on this issue.

[1] I guess that makes this JIRA disappear wrt release notes, since we don't have a process
of updating the ones posted on the Derby site. The tool generating the release notes will
trust JIRA, so it will exclude this issue when generating release notes for, say, 10.9.

> 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