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-3324) JDBC statement cache implementation
Date Tue, 29 Jan 2008 09:24:34 GMT

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

Kristian Waagan updated DERBY-3324:
-----------------------------------

    Attachment: derby-3324-1d-jdbc_statementcache.diff

'derby-3324-1d-jdbc_statementcache.diff' deprecates version 1c and contains only two changes.
I removed the redundant null check Knut Anders commented on and fixed some bad formatting
in the string created by StatementKey.toString.

> JDBC statement cache implementation
> -----------------------------------
>
>                 Key: DERBY-3324
>                 URL: https://issues.apache.org/jira/browse/DERBY-3324
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Network Client
>    Affects Versions: 10.4.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.4.0.0
>
>         Attachments: derby-3324-1a-jdbc_statementcache.diff, derby-3324-1a-jdbc_statementcache.stat,
derby-3324-1b-jdbc_statementcache.diff, derby-3324-1b-jdbc_statementcache.stat, derby-3324-1c-jdbc_statementcache.diff,
derby-3324-1c-jdbc_statementcache.stat, derby-3324-1d-jdbc_statementcache.diff
>
>
> Implement a cache for storing JDBC prepared statement objects.
> The cache will be responsible for holding free prepared statement objects that can be
reused, and also to throw away objects if the cache grows too big.
> All objects in the cache must belong to the same physical connection, but they can be
reused across logical connections obtained from a single physical connection in a connection
pool.
> This component is probably a candidate for code sharing between the client and the embedded
driver. Sharing will not  be part of this issue.

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