Add migration version-check function #58
Merged
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
rod-glover
requested review from
jameshiebert,
corviday and
nikola-rados
and removed request for
jameshiebert and
corviday
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.
This PR adds a function that checks the migration version of the database in use against the latest migration version in the repo. Resolves #57 .
Question: Should this function be invoked automatically when
pycds.Base.create_all()is invoked? That would ensure all client code must be using a version-compatible release of PyCDS, but it may be too meddlesome. @jameshiebert ?I'm tending toward "no" on this question, and it can easily be added in a later PR.