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-3313) JDBC client driver statement cache
Date Thu, 11 Sep 2008 15:21:45 GMT

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

Kristian Waagan closed DERBY-3313.
----------------------------------


Closing the issue, as there is no more work planned.
The feature has gone through initial testing (code inspection, Derby regression tests and
an enterprise level benchmark) and documentation has been added.

> JDBC client driver statement cache
> ----------------------------------
>
>                 Key: DERBY-3313
>                 URL: https://issues.apache.org/jira/browse/DERBY-3313
>             Project: Derby
>          Issue Type: New Feature
>          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