add some kind of check to ensure the database schema revision is compatible with the api version being run #18
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
High Priority
invalid
question
reproduction needed
schema-fix-required
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ClassClock/API#18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
it might be helpful to have the api check the current database version (i.e. the alembic version stamp) when it starts up to make sure that the database schema it is running against is compatible with that version