[
https://issues.apache.org/jira/browse/DERBY-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615890#action_12615890
]
Kristian Waagan commented on DERBY-3779:
----------------------------------------
Kim, thanks for looking at this. See my comments below.
-----
The only user-visible API change for this feature seems to be the addition of
the maxStatements property to ClientConnectionPoolDataSource. Is that correct?
-----
Yes, and it is also true for ClientConnectionPoolDataSource40.
------
I assume that a developer must use these data sources in order to use statement
caching.
-----
Correct.
-----
I'm assuming that you'd also have to set various other connection properties
before calling getPooledConnection().
----
Yes, you also have to set whatever other properties you need to connect to your
database. getPooledConnection creates the physical connection to the database,
PooledConnection.getConnection() creates a logical connection. The typical
usage is that you create many logical connections off the physical one, but
only one can be active at any given time. Also, as soon as a new logical
connection is created, the previous one is closed.
-----
This new feature belongs in the Admin Guide, since that is where the client
driver is discussed.
-----
That makes sense, currently the feature is for the client driver only.
A user will (transparently) interact with the cache through
Connection.prepareStatement/-Call and
PreparedStatement/CallableStatement.close. The former possibly takes a
statement out of the cache, the latter possibly puts a statement into the cache.
> 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: 10.4.1.4, 10.5.0.0
> Reporter: Kristian Waagan
> Assignee: Kim Haase
> Priority: Minor
>
> 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 repository).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
