db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1479) Documentation should note need to upgrade databases in jars
Date Wed, 12 Jul 2006 00:02:30 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1479?page=comments#action_12420464 ] 

Daniel John Debrunner commented on DERBY-1479:
----------------------------------------------

This is a bug, not a documentation issue. Derby should be able to boot in soft-upgrade mode
against databases in jars or databases on read-only media.
I thought there was an existing bug, but I can't find it yet.

> Documentation should note need to upgrade databases in jars
> -----------------------------------------------------------
>
>          Key: DERBY-1479
>          URL: http://issues.apache.org/jira/browse/DERBY-1479
>      Project: Derby
>         Type: Bug

>   Components: Documentation
>     Versions: 10.1.3.1, 10.1.2.1, 10.1.1.0
>     Reporter: Andrew McIntyre
>      Fix For: 10.1.3.2, 10.1.4.0, 10.2.0.0
>  Attachments: jartest3.jar
>
> The documentation currently does not address the need to upgrade databases in jars when
connecting to a newer version of Derby.
> For example, attempting to connect to a database in a jar created with Derby 10.0 fails
when trying to connect with Derby 10.1. The following error is thrown:
> ERROR XJ040: Failed to start database 'jar:(pathtojarfile)pathinjar', see the next exception
for details.
> ERROR 40XD1: Container was opened in read-only mode. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message