db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3313) JDBC client driver statement cache
Date Thu, 10 Jan 2008 18:04:34 GMT

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

Daniel John Debrunner commented on DERBY-3313:
----------------------------------------------

Just to be clear, the overview says the embedded driver already has a statement cache, but
I think it's a different type of cache. The embedded driver caches statement plans (not JDBC
statement objects) that can be shared across multiple connections, I think you are planning
to cache JDBC statement objects for a specific connection. If you are planning the latter
then you may want to think about the fact that this would also be useful in an embedded environment,
thus maybe the code could be made to work for both? Not a requirement, but something to think
about.

> 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.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>             Fix For: 10.4.0.0
>
>         Attachments: 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.


Mime
View raw message