Implement a database upgrade system, use it to fix v12 db #107
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
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.
In v12, the ItemId column in UserInfoRec was changed from a
stringto aGuid(#97). In v13, released 3 days later, it was changed back to astring(#100). However, anyone who added media to their library with v12 now has unusable database entries since the types no longer match.This PR adds a generic system for upgrading the database and uses it to convert any
Guidtypes back to strings.Fixes #104.
I'm leaving this as a draft since I don't currently have access to my Jellyfin server to test it, although it should™ be good to go if others would like to test it first (with a db backup!).