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 "Andrew McIntyre (JIRA)" <de...@db.apache.org> on 2006/07/31 23:38:16 UTC

[jira] Updated: (DERBY-1479) Release note for DERBY-541 on 10.1.3.1 release page

     [ http://issues.apache.org/jira/browse/DERBY-1479?page=all ]

Andrew McIntyre updated DERBY-1479:
-----------------------------------

    Summary: Release note for DERBY-541 on 10.1.3.1 release page  (was: Documentation should note need to upgrade databases in jars)

Changing description to more accurately reflect what was done to resolve the issue. 

> Release note for DERBY-541 on 10.1.3.1 release page
> ---------------------------------------------------
>
>                 Key: DERBY-1479
>                 URL: http://issues.apache.org/jira/browse/DERBY-1479
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1
>            Reporter: Andrew McIntyre
>             Fix For: 10.1.3.2, 10.1.4.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