[
https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3326:
-----------------------------------
Attachment: derby-3326-3c-new_classes.diff
'derby-3326-3c-new_classes.diff' contains some changes from the earlier
versions, but the design is the same.
I will commit this later today and use it as a baseline for further work,
unless someone want time to review it before it goes in.
I expect there will be some changes later, and please note that the patch in
partial and does not enable any of the statement pooling code.
> Introduce a caching logical connection and logical prepared statement in the
> client driver
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-3326
> URL: https://issues.apache.org/jira/browse/DERBY-3326
> Project: Derby
> Issue Type: Sub-task
> Components: JDBC, Network Client
> Affects Versions: 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.4.0.0
>
> Attachments: derby-3326-1a_cpds_testing_preparation.diff,
> derby-3326-1a_cpds_testing_preparation.stat,
> derby-3326-1b_cpds_testing_preparation.diff,
> derby-3326-2a-method_rename.diff, derby-3326-3a-new_classes.diff,
> derby-3326-3a-new_classes.stat, derby-3326-3b-new_classes.diff,
> derby-3326-3b-new_classes.stat, derby-3326-3c-new_classes.diff
>
>
> A logical connection with statement caching capabilities is required to
> support JDBC prepared statement pooling. Further, a logical prepared
> statement object is also needed.
> The logical prepared statements will be generated by the logical connection's
> 'prepareStatement'-method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
