You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2009/05/18 13:15:45 UTC
[jira] Resolved: (DERBY-4204) Runtime statistics not collected on
re-execution of statement
[ https://issues.apache.org/jira/browse/DERBY-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-4204.
---------------------------------------
Resolution: Fixed
Derby Info: [Regression] (was: [Patch Available, Regression])
Marking the issue as resolved since the fix has been committed to trunk and to the 10.5 branch.
> 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
> Fix For: 10.5.1.2, 10.6.0.0
>
> 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/%3c8a0216de0904291334j4bc715c3s6d46fb65e5953659@mail.gmail.com%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.