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 Thu, 28 Feb 2008 15:41:51 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-1b-enable_statement_pooling.diff

'derby-3329-1b-enable_statement_pooling.diff' is an updated patch, with the following changes:
 a) Initiate state before publishing reference to self (moved code).
 b) Moved code not throwing exception out of try-catch block (refactoring)
 c) Added method isStatementPoolingEnabled.
    Use of method is twofold:
      - by NetConnection to determine value of doCloseStatementsOnClose_
      - by LogicalConnection, forwarded into am.Connection to use correct close procedure.
       (requires another patch)

I hope this patch will go in shortly, and will post a new patch actually enabling statement
The enabling patch will only edit a few lines.

> 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, derby-3329-1b-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