[jira] Issue Comment Edited: (DERBY-4157) Create a test to verify that virgin metadata is identical to hard-upgraded metadata

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

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

Knut Anders Hatlen edited comment on DERBY-4157 at 6/24/09 3:41 PM:
--------------------------------------------------------------------

Google's calculator agrees: <URL:http://www.google.com/search?q=%282^14-14-1%29+*+10+seconds>
:)

      was (Author: knutanders):
    Google's calculator agrees: http://www.google.com/search?q=%282^14-14-1%29+*+10+seconds
:)
  
> 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: Test
>          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.