Upgrading databases #143
Merged
Upgrading databases #143
Conversation
This file contains 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
Currently takes in a suffix (which could be the empty string if the file should be replaced) and outputs the upgraded database with the suffix appended to the filename (before the file extension)
EdgesFTW
commented
Nov 9, 2023
and now updates schema_version constant to 3
matthiasdiener
force-pushed
the
upgrading-DBs
branch
from
ece71b2 to
1e35b4a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #99. This feature should provide a script that will upgrade previous databases to the current schema (version 3).
Overview of known changes between schema versions:
warnings.rankwarnings.unixtime,loggingOriginally posted by @matthiasdiener in #99 (comment)
Additional Docs:
