db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4157) Create a test to verify that virgin metadata is identical to hard-upgraded metadata
Date Tue, 21 Jul 2009 20:08:14 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733799#action_12733799
] 

Rick Hillegas commented on DERBY-4157:
--------------------------------------

Attaching derby-4157-03-aa-branchBug.diff. This patch changes the test for the discrepancies
described in DERBY-4214. Previously, we ignored those diffs for trajectories which ended at
the 10.5.1.1 release. Now that we have a 10.5.2.0 release, the test needs to be broadened
to all trajectories which end at the 10.5 branch. Committed at subversion revision 796517.

> Create a test to verify that virgin metadata is identical to hard-upgraded metadata
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-4157
>                 URL: https://issues.apache.org/jira/browse/DERBY-4157
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.6.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-4157-01-aa-refactor.diff, derby-4157-02-aa-newtest.diff, derby-4157-02-ab-newtest.diff
>
>
> We should write a test to verify that the metadata is correct for each release for all
hard-upgrade trajectories which terminate in that release. The test should examine all system
tables. Note that if there are N releases, then there will (2<sup>N</sup> - N)
- 1 trajectories to examine.

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


Mime
View raw message