Remove legacy backup conversion code #2351
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d this anymore, and it causes problems in backups with different passwords
duncdrum
added
the
needs documentation
|
we should note this change for prosperity in |
dizzzz
approved these changes
Dec 16, 2018
|
@duncdrum docs as requested - eXist-db/documentation#294 |
duncdrum
removed
the
needs documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This code converts an old style eXist-db user database to a new style one when restoring a backup. This stuff is from pre-2.2 days. I really don't think we need this anymore. Not to mention that it does not actually work correctly if the backup and the database have different admin passwords.