[ http://issues.apache.org/jira/browse/DERBY-1479?page=comments#action_12420501 ]
Daniel John Debrunner commented on DERBY-1479: ---------------------------------------------- I wouldn't document this in the 10.2 docs because it won't be an issue there. I guess one could document it in the 10.1 docs, but seems somewhat strange to me, have other bugs been documented in existing documentation, apart from the release notes? > 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.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
