You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2009/06/23 14:45:08 UTC
[jira] Updated: (DERBY-4154) DboPowersTest should not hard upgrade
the system/wombat database
[ 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: 10.4.2.0, 10.5.1.1, 10.6.0.0
> 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.