Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2086637307.1242313245780.JavaMail.jira@brutus>
Date: Thu, 14 May 2009 08:00:45 -0700 (PDT)
From: "Bryan Pendleton (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4204) Runtime statistics not collected on
 re-execution of statement
In-Reply-To: <1998839345.1241079450516.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Pendleton updated DERBY-4204:
-----------------------------------

    Attachment: addXPLAINTestUsingCOUNT.diff

Revised the new test slightly to make it more compact, by issuing
a COUNT query and using JDBC.assertFullResultSet to check the result.

> 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: 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.