[
https://issues.apache.org/jira/browse/DERBY-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615794#action_12615794
]
Kim Haase commented on DERBY-3779:
----------------------------------
The only user-visible API change for this feature seems to be the addition of
the maxStatements property to ClientConnectionPoolDataSource. Is that correct?
I would expect this feature also to work for ClientConnectionPoolDataSource40,
though I don't see any explicit statement to this effect in DERBY-3313 or its
subtasks (I might have missed it, though). Is that true?
I assume that a developer must use these data sources in order to use statement
caching.
The package.html file has sample code that does the following (comments
removed):
ClientConnectionPoolDataSource cpds = new ClientConnectionPoolDataSource();
cpds.setMaxStatements(20);
PooledConnection pc = cpds.getPooledConnection();
I'm assuming that you'd also have to set various other connection properties
before calling getPooledConnection().
This new feature belongs in the Admin Guide, since that is where the client
driver is discussed. (The Developer's Guide deals almost entirely with the
embedded driver.) The information should probably be added to
cadminnsdatasources.dita (Accessing the Network Server by using a DataSource),
and another example should be added to the subtopic radminnsdatasourcexmp.dita
(DataSource access example) showing the use of the statement cache. Does this
make sense? I'll see if there are other places where it would make sense to
mention statement caching.
> 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.
