[
https://issues.apache.org/jira/browse/DERBY-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3324:
-----------------------------------
Attachment: derby-3324-1a-jdbc_statementcache.stat
derby-3324-1a-jdbc_statementcache.diff
'derby-3324-1a-jdbc_statementcache.diff' is the first iteration of a JDBC
statement cache implementation.
I'm a bit short on time right now, so there won't be too much comments...
Please read the comments of DERBY-3313 for the overview. I have redone the
statement key hierarchy, and I would especially appreciate some feedback on the
hash code generation. JDBCStatementCache, StatementKey and StatementKeyFactory
are the classes that are visible outside the package.
I need to write a few more tests, but thought I'd give people the chance to
have a look at the code over the weekend ;)
The patch will enable some tests, but none of the new code will be used by
Derby yet.
Patch ready for review.
> JDBC statement cache implementation
> -----------------------------------
>
> Key: DERBY-3324
> URL: https://issues.apache.org/jira/browse/DERBY-3324
> Project: Derby
> Issue Type: Sub-task
> Components: Network Client
> Affects Versions: 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.4.0.0
>
> Attachments: derby-3324-1a-jdbc_statementcache.diff,
> derby-3324-1a-jdbc_statementcache.stat
>
>
> Implement a cache for storing JDBC prepared statement objects.
> The cache will be responsible for holding free prepared statement objects
> that can be reused, and also to throw away objects if the cache grows too big.
> All objects in the cache must belong to the same physical connection, but
> they can be reused across logical connections obtained from a single physical
> connection in a connection pool.
> This component is probably a candidate for code sharing between the client
> and the embedded driver. Sharing will not be part of this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
