db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4154) DboPowersTest should not hard upgrade the system/wombat database
Date Tue, 23 Jun 2009 12:45:08 GMT

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

Dag H. Wanvik updated DERBY-4154:

    Attachment: derby-4154.diff

Uploading a patch for this, which makes the hard upgrade use another database,
by wrapping the offending test cases in a singleUseDatabaseDecorator.
I manually tested this by creating a system/wombat with a 10.4 release and
then ran the test against trunk (with derby.database.allowPreReleaseUpgrade=true)
and verified that after the run, I could still connect to system/wombat with a 10.4 Derby.

Running full regressions now. Ready for review.

> DboPowersTest should not hard upgrade the system/wombat database
> ----------------------------------------------------------------
>                 Key: DERBY-4154
>                 URL: https://issues.apache.org/jira/browse/DERBY-4154
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:,,
>            Reporter: Kathey Marsden
>         Attachments: derby-4154.diff
> In order to test soft upgrade it is nice to be able to run tests against a soft upgraded
database. This currently cannot be done because DboPowersTest  hard upgrades system/wombat.
It should do it's hard upgrade test against another database.

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

View raw message