Use peewee-moves for database migrations #62
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
dougthor42
force-pushed
the
db-migrations-peewee-moves
branch
from
2d718ae
to
3c3d3c1
Compare
2 tasks
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.
I plan on making changes to the database schema in the future, and we need to have migrations in place to support those changes.
I've chosen
peewee-movesas our migration tool, winning out overpeewee-migrate(andpeewee-db-evolve, but I think that might actually solve a different problem...`)Why did I choose
peewee-moves? At the time of this writing, the documentation forpeewee-moveswas better and I was actually able to get it to work. That said,peewee-migrateappears to be more popular (by GitHub star count).