[
https://issues.apache.org/jira/browse/DERBY-3313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559978#action_12559978
]
Kristian Waagan commented on DERBY-3313:
----------------------------------------
I have spent some time looking into code sharing and have come to the
conclusion that I will not deal with it at this time.
There was lots of discussion a while ago, but no viable/acceptable solution for
enabling "proper" code sharing was found.
My decision is based on the limited time until feature freeze, and on my
impression that code sharing can be a hard nut to crack.
I do however still believe parts of the code can be shared between the embedded
and the client driver, specifically the implementation of the cache itself
(currently located in the "am.stmtcache" package).
> 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: derby-3313-1a-early_prototype.diff,
> derby-3313-1a-early_prototype.stat, 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.
