refactor: store DB version inside versions table
#1058
Merged
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.
Summary
This PR starts storing the DB version inside of a new
versionstable instead of the ill-namedpreferencestable.preferencestable, set to be removed in a future TagStudio versionversionstablekeycolumn and an intvaluecolumnkeycolumn stores one of two values:'INITIAL'and'CURRENT''INITIAL'stores the database version number in which in was created100'CURRENT'stores the current database version numberTasks Completed