Skip to content

Note on upgrading 2.2 and earlier to eXist-db 5.0.0+ #294

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 4, 2019
Merged

Note on upgrading 2.2 and earlier to eXist-db 5.0.0+ #294

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions src/main/xar-resources/data/upgrading/upgrading.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,10 +20,10 @@
<para>The primary goal of an upgrade is to migrate your eXist application to a new version,
while preserving the contents of your database.</para>
<para>Before embarking on an upgrade, you should first review the new version's release notes
(see the <link xlink:href="http://exist-db.org/exist/apps/wiki/blogs/eXist/" condition="_blank">eXist
Developer's Blog</link> for an archive of all past release notes). The release notes
introduce the new version's features, improvements and bug fixes. They can also outline any
new requirements (for instance the required version of Java). </para>
(see the <link xlink:href="http://exist-db.org/exist/apps/wiki/blogs/eXist/"
condition="_blank">eXist Developer's Blog</link> for an archive of all past release notes).
The release notes introduce the new version's features, improvements and bug fixes. They can
also outline any new requirements (for instance the required version of Java). </para>
<para>For the purpose of this guide, the most important item in the release notes is whether the
new version is <emphasis>binary-compatible</emphasis> with the previous version or not. Pay
close attention to these notes, as they will tell you which upgrade route to follow.</para>
Expand Down Expand Up @@ -176,6 +176,9 @@
<para>If a non-incremental upgrade across multiple non-compatible releases is necessary,
for instance from 1.4 to 3.6, we strongly recommend to first check past release notes to understand
how breaking changes might affect you.</para>
<important><para>Note, database backups from eXist-db 2.2 and earlier are not compatible with eXist-db
5.0.0+. If you wish to migrate to eXist-db version 5.0.0+ from version 2.2 or earlier, you
should first upgrade (incrementally if nessecary) to the latest 4.x.x version.</para></important>
<table xml:id="old-news">
<title>Notes on previous releases</title>
<tgroup cols="2">
Expand Down