Database upgrade/migration path #24
At some point after the first stable release, we're bound to introduce a breaking change to the database. We need a mechanism to automatically upgrade the Telodendria database by converting schema upon the first run after an upgrade. It may be worth thinking about how this mechanism will work sooner rather than later.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?