db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4843) Consult isPoolable hint before caching prepared statement
Date Wed, 13 Oct 2010 12:16:32 GMT

    [ 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:,,,
>            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.

View raw message