[
https://issues.apache.org/jira/browse/DERBY-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706888#action_12706888
]
Bryan Pendleton commented on DERBY-4204:
----------------------------------------
In the trunk, it would be neat if we could write a test case for this using the
new XPLAIN tables feature.
I don't think we want to do that for the base patch because it would then be
hard to back-port the
patch to 10.5 and earlier.
But if you let me know when you're done with the basic patch, I'll try writing
a separate test-only
patch for the trunk which uses the XPLAIN tables feature to confirm this fix.
> 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: 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.
