Add database migrations
Nowadays upgrading TimeRanger each minor version requires a manual migration of database. We should automate this process by implementing:
- A table in database to hold information about applied migrations
- An interface representing a migration
- A class which holds migration's data
- A class which does manage migrations
- A default export method that allows to save current database as another file in file system
- A default import method that determines database version and automatically applies required migrations
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information