db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4204) Runtime statistics not collected on re-execution of statement
Date Thu, 30 Apr 2009 08:21:31 GMT

     [ 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, the last call to syscs_get_runtimestatistics returns the following:

Statement Name: 
Statement Text: 
	insert into t values 1

With (and later), it returns this:

Statement Name: 
Statement Text: 
	values syscs_util.syscs_get_runtimestatistics()

The behaviour in 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:
>            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 and Derby, 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.

View raw message