[
https://issues.apache.org/jira/browse/DERBY-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-4204:
--------------------------------------
Attachment: repro.sql
Here's a script that reproduces the problem.
With Derby 10.2.2.0, the last call to syscs_get_runtimestatistics returns the
following:
Statement Name:
null
Statement Text:
insert into t values 1
.
.
.
With 10.3.1.4 (and later), it returns this:
Statement Name:
null
Statement Text:
values syscs_util.syscs_get_runtimestatistics()
.
.
.
The behaviour in 10.2.2.0 is the expected one, since the insert statement was
the last one to be executed before syscs_get_runtimestatistics was called.
Re-execution of select statements appears to work as expected.
> 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
> Priority: Minor
> Attachments: repro.sql
>
>
> 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.
