[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

["Kristian Waagan (JIRA)" <ji...@apache.org>]

     [ 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-2a-method_rename.diff

'derby-3326-2a-method_rename.diff' renames the method ClientPooledConnection.trashConnection to informListeners, as this reflects better what the method does.

> 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
>
>
> 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.