db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver
Date Sat, 16 Feb 2008 15:31:09 GMT

     [ 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-3b-new_classes.stat
                derby-3326-3b-new_classes.diff

'derby-3326-3b-new_classes.diff' is a new version with changes in LogicalStatementEntity and
a test.
The test is a package private test, and can be built and run with 'ant pptesting junit-pptesting'.

It is hard to write a proper "normal" test, as statement pooling is supposed to be transparent
to the user and there are no methods to obtain information about the cache itself etc.
The only ideas I have come up with so far, is making sure it is enabled (by checking implementation
details, like which class is used), and making sure nothing fails if you overflow the cache
etc.

To test the logical forwarding classes, I will identify some suitable existing tests and run
them with a connection pool data source decorator.

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


Mime
View raw message