Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <22523476.1179255796394.JavaMail.jira@brutus>
Date: Tue, 15 May 2007 12:03:16 -0700 (PDT)
From: "A B (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2641) Convert lang/staleplans.sql to JUnit
In-Reply-To: <27969382.1179133996134.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-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496089 ] 

A B commented on DERBY-2641:
----------------------------

> Do you have any ideas?

Nothing comes to mind, no.  The easiest way to change a plan is via DDL (ex. add/drop an index), but I think those will invalidate a plan, which would defeat the purpose of the stale plans test.

> We could of course leave the test as it is and explain in the comments that the first test case no
> longer tests stale plans.

Given that the goal of this issue is to "convert" the test and not necessarily to "fix" it, I think this is fine.  If further work is required to make the first part of the test more meaningful, that could easily be a separate Jira...

> Convert lang/staleplans.sql to JUnit
> ------------------------------------
>
>                 Key: DERBY-2641
>                 URL: https://issues.apache.org/jira/browse/DERBY-2641
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: derby-2641-1.diff, derby-2641-1.stat
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.