[
https://issues.apache.org/jira/browse/DERBY-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616979#action_12616979
]
Kathey Marsden commented on DERBY-3797:
---------------------------------------
The test was originally added in a bug fix that metadata calls were taking too
long a time when executed with mutiple connections. This was the checkin
comment:
if we do need to create SPS during metadata calls (eg., in SPS dynamic
mode), we'd better do it in nested transaction, to be consistent with
our SPS recompile, although this has the disadvantage of the possibility
of blocking in child transaction with parent, especially in "serializable"'
So I think the general intention of the test was to test metadata calls when
executed with multiple connections, and perhaps the author was not thorough in
checking the actual results. Anything you add to improve that would be welcome.
> Convert jdbcapi/metadataMultiConn to JUnit.
> -------------------------------------------
>
> Key: DERBY-3797
> URL: https://issues.apache.org/jira/browse/DERBY-3797
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.5.0.0
> Reporter: Erlend Birkenes
> Assignee: Erlend Birkenes
> Priority: Minor
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
