db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-2221) Cannot re-connect to 10.0 database after soft upgrade with 10.3 (trunk) code
Date Thu, 24 May 2007 00:10:16 GMT

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

Daniel John Debrunner closed DERBY-2221.

I rebuilt the jars files from svn revision 494201 which corresponds to the first working version
of the JUnit upgrade tests and the version for this bug.

Running the 494201 tests failed on 10.0 and passed on all others as this bug states.

Changing to use a trunk version of derby.jar (from today) while continuing to use derbyTesting.jar
from 494201 passed on all old versions including 10.0. I.e. no problem with the latest version
of derby.

Thus I believe that this bug has been fixed by other changes.

> Cannot re-connect to 10.0 database after soft upgrade with 10.3 (trunk) code
> ----------------------------------------------------------------------------
>                 Key: DERBY-2221
>                 URL: https://issues.apache.org/jira/browse/DERBY-2221
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure, SQL
>    Affects Versions:
>            Reporter: Daniel John Debrunner
>         Assigned To: Mike Matrigali
> Database fails to start with after a 10.3 database has connected to it. Caused
by a NullPointerException.
> Even if 10.0 is not a common starting point it would be good to track down what is causing
this, it seems to be some on-disk format
> of an object has changed in an incompatible way.
> To reproduce run the JUnit upgrade test added by DERBY-2217
> org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite 
> setting the system property derbyTesting.jar.path to point to a folder that contains
a release in the folder

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

View raw message