[
https://issues.apache.org/jira/browse/DERBY-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918785#action_12918785
]
Lily Wei commented on DERBY-4834:
---------------------------------
+1 for me. Do we need other system utility such as locks certain table (or all
the tables) is holding, how many open statement or transaction in the system? I
thought it might be useful for certain to also understand the stage/resource of
derby system.
> Add helper class for working with index statistics in JUnit tests
> -----------------------------------------------------------------
>
> Key: DERBY-4834
> URL: https://issues.apache.org/jira/browse/DERBY-4834
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.7.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: derby-4834-1a-indexstats_utility_class.diff
>
>
> Dealing with index statistics in the JUnit tests require some tedious work,
> like looking up table and index ids, doing selects on the SYS.SYSSTATISTICS
> table, and analyzing the results of these queries.
> To make life easer and the tests easier to read, a set of utility methods
> will be added to a new class living in the JUnit test framework package.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
