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-3313) JDBC client driver statement cache
Date Tue, 08 Jul 2008 07:10:36 GMT

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

Knut Anders Hatlen commented on DERBY-3313:

The description looks very good to me. It would be good if some of this information could
also be put into one of the manuals. I think most of it could be copied directly.

> 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:
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>             Fix For:
>         Attachments: bank_transaction_stmtcache_16c.png, derby-3313-1a-early_prototype.diff,
derby-3313-1a-early_prototype.stat, JDBCClientStatementCacheOverview.txt, JDBCClientStatementCacheOverview.txt,
> 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.

View raw message