db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Wooldridge (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3313) JDBC client driver statement cache
Date Wed, 25 Nov 2009 10:54:39 GMT

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

Brett Wooldridge commented on DERBY-3313:
-----------------------------------------

I would like to re-open this issue.  Prepared statement caching is still needed on XA connections.


> JDBC client driver statement cache
> ----------------------------------
>
>                 Key: DERBY-3313
>                 URL: https://issues.apache.org/jira/browse/DERBY-3313
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Network Client
>    Affects Versions: 10.4.1.3
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>             Fix For: 10.4.2.0
>
>         Attachments: bank_transaction_stmtcache_16c.png, derby-3313-1a-early_prototype.diff,
derby-3313-1a-early_prototype.stat, JDBCClientStatementCacheOverview.txt, JDBCClientStatementCacheOverview.txt,
package.html, package.html
>
>
> A statement cache in the JDBC client driver will help increase performance in certain
scenarios, for instance some multi-tier systems using connection pooling.
> Please consult the comments and documents attached to this issue for more information.

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


Mime
View raw message