[
https://issues.apache.org/jira/browse/DERBY-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564349#action_12564349
]
Kristian Waagan commented on DERBY-3325:
----------------------------------------
Thanks for looking at the test Myrna.
I also want to add that I did not see an easy way to extend the test to handle
different attributes, and that was the main reason why I started studying it
and rewriting it.
Further, I think that the test is a good one! It had already discovered the
problem with JDBC 4.0 data sources (DERBY-2559), and it started failing when I
introduced the maxStatements property (for various problems with the addition).
It has helped me a lot already :)
I created DERBY-3369 to track extension of the test.
> Add 'maxStatements' property to ClientConnectionPoolDataSource
> --------------------------------------------------------------
>
> Key: DERBY-3325
> URL: https://issues.apache.org/jira/browse/DERBY-3325
> Project: Derby
> Issue Type: Sub-task
> Components: JDBC, Network Client
> Affects Versions: 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.4.0.0
>
> Attachments: DataSourceReferenceTest.diff,
> DataSourceReferenceTest.java, derby-3325-1a-maxStatements.diff,
> derby-3325-1a-maxStatements.stat
>
>
> The classes in Derby implementing javax.sql.ConnectionPoolDataSource must
> provide setter and getter methods for the property 'maxStatements'.
> This property is used to control the whether the data source should produce
> pooled connections with statement cache capabilities or not, and how big the
> statement cache is allowed to be.
> This issue only deals with 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.
