[
https://issues.apache.org/jira/browse/DERBY-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709436#action_12709436
]
Knut Anders Hatlen commented on DERBY-4204:
-------------------------------------------
Thanks for writing the test, Bryan! The test looks much better now that the
boilerplate is removed. +1 to commit.
(One microscopic nit: assertSingleValueResultSet() would simplify the code
slightly compared to assertFullResultSet(). And there's a typo in a comment:
s/caputured/captured/)
> Runtime statistics not collected on re-execution of statement
> -------------------------------------------------------------
>
> Key: DERBY-4204
> URL: https://issues.apache.org/jira/browse/DERBY-4204
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.3.1.4
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Attachments: addXPLAINTest.diff, addXPLAINTestUsingCOUNT.diff,
> d4204.diff, repro.sql, test.diff
>
>
> Runtime statistics are only collected the first time an insert/update/delete
> statement is executed. The behaviour changed between Derby 10.2.2.0 and Derby
> 10.3.1.4, so this was likely introduced by DERBY-827.
> Reported on derby-dev:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200904.mbox/%[email protected]%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
