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/07 13:23:30 UTC
[jira] Updated: (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 updated DERBY-4204:
--------------------------------------
Attachment: test.diff
Attached is a patch that adds JUnit test cases that test collection of runtime statistics for SELECT, UPDATE, INSERT, DELETE, VALUES and CALL when re-executing a prepared statement. The test cases for SELECT and VALUES pass, the rest of them fail.
> 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/%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.