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-3329) Enable statement pooling in the client JDBC driver
Date Fri, 15 Feb 2008 17:30:08 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kristian Waagan updated DERBY-3329:

    Attachment: derby-3329-1a-enable_statement_pooling.diff

'derby-3329-1a-enable_statement_pooling.diff' modifies ClientPooledConnection.java and enables
statement pooling under the following preconditions:
 * Patches for DERBY-3326 and DERBY-3328 must be applied.
 * Connections must be obtained through a ClientConnectionPoolDataSource
 * The property "maxStatements" must be set to something larger than zero in CCPDS.

Note that statement pooling is not enabled for XA connections yet. That would require a trivial
change in ClientPooledConnection and addition of the "maxStatements" property in the XA data

Note that there are no proper testing yet, but I have run through jdbc4.ConnectionTest and
jdbc4.PreparedStatementTest without errors (with statement pooling enabled).
Tests will follow in a separate patch.

Patch ready for review.

> Enable statement pooling in the client JDBC driver
> --------------------------------------------------
>                 Key: DERBY-3329
>                 URL: https://issues.apache.org/jira/browse/DERBY-3329
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC, Network Client
>    Affects Versions:
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Trivial
>             Fix For:
>         Attachments: derby-3329-1a-enable_statement_pooling.diff
> Enable statement pooling in the client JDBC driver.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message