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] Commented: (DERBY-3779) Add client side JDBC statement pool documentation
Date Thu, 31 Jul 2008 09:36:31 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618627#action_12618627

Kristian Waagan commented on DERBY-3779:

I think the documentation looks good.
The following sentence caught my attention though:
"Next, use a javax.sql.PooledConnection object to obtain a physical connection, and a javax.sql.Connection
object to obtain a logical connection."

You use ClientConnectionPoolDataSource.getPooledConnection to obtain the physical connection,
the PooledConnection object is the physical connection. Then you use PooledConnection.getConnection
to obtain the logical connection, which will implement java.sql.Connection just as a "normal"
connection would. Do you see a way to rewrite the sentence?
The piece of information that you need to use getPooledConnection is important, because I
think Derby has a getConnection method on the ClientConnectionPoolDataSource object. Using
the latter method will not enable statement caching.

BTW; PooledConnection is in the package javax.sql, whereas Connection is in java.sql.


> Add client side JDBC statement pool documentation
> -------------------------------------------------
>                 Key: DERBY-3779
>                 URL: https://issues.apache.org/jira/browse/DERBY-3779
>             Project: Derby
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions:,
>            Reporter: Kristian Waagan
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-3779.diff, DERBY-3779.stat, DERBY-3779.zip
> Document the new feature client side JDBC statement cache in the manual(s).
> As a starter, see DERBY-3313 and the package.html file (or browse it from the Subversion

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

View raw message