[
https://issues.apache.org/jira/browse/DERBY-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan resolved DERBY-6086.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.10.0.0
Issue & fix info: (was: Patch Available)
Thanks, Dag.
I removed the comment in patch 1b. I added it in the first place to avoid
questions about where I got the magical number 7 from.
Committed patch 1b to trunk with revision 1448956.
> Factor out logic for creating custom connection in
> jdbcapi.StatementPoolingTest
> -------------------------------------------------------------------------------
>
> Key: DERBY-6086
> URL: https://issues.apache.org/jira/browse/DERBY-6086
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.10.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.10.0.0
>
> Attachments: derby-6086-1a-logical_con_boilerplate.diff,
> derby-6086-1b-logical_con_boilerplate.diff
>
>
> There is quite a bit of common boilerplate code in
> jdbcapi.StatementPoolingTest related to getting a custom connection, or
> rather more than one logical connection from a single pooled (physical)
> connection.
> This could be factored out to make the test methods shorter, and to make the
> test methods more focused on whatever they're testing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
