Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <13376754.1179251836330.JavaMail.jira@brutus>
Date: Tue, 15 May 2007 10:57: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_12496069 ] 

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

> I will update the comments in the test to make it clear that the index scans are intended.

Next question then would be: is the test still testing what it's trying test?  I.e. if it uses an index scan with 1 row and it uses an index scan with 10 rows (I think that's what it's doing), then will we be able to see the changed (or not changed) plans as the test expects?  I haven't looked in detail, it's just something that occurred to me while scanning the old .sql script...

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