We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, any schema change results in a breaking release (old DBs will not work and either need to be deleted or manually edited).
We could use alembic (part of the SQLAlchemy project) to automatically compare the saved DBs to the data model, automatically generating and applying migrations. See https://alembic.sqlalchemy.org/en/latest/autogenerate.html#what-does-autogenerate-detect-and-what-does-it-not-detect
alembic
Alternatively, we could set up alembic to run manually written (or automatically generated then manually reviewed/edited) migrations.
The text was updated successfully, but these errors were encountered:
This seems relevant for going full auto https://alembic.sqlalchemy.org/en/latest/cookbook.html#run-alembic-operation-objects-directly-as-in-from-autogenerate
Sorry, something went wrong.
Still needs some more testing, but got a basic implementation working. It detects and adds the new column on my old origin-less db:
2024-05-15 17:09:05,011 - alembic.autogenerate.compare - INFO - Detected added column 'country.origin'
Use alembic to automatically migrate game DBs (#153)
3995ce9
Closes #151
MichaelMakesGames
Successfully merging a pull request may close this issue.
Currently, any schema change results in a breaking release (old DBs will not work and either need to be deleted or manually edited).
We could use
alembic
(part of the SQLAlchemy project) to automatically compare the saved DBs to the data model, automatically generating and applying migrations. See https://alembic.sqlalchemy.org/en/latest/autogenerate.html#what-does-autogenerate-detect-and-what-does-it-not-detectAlternatively, we could set up alembic to run manually written (or automatically generated then manually reviewed/edited) migrations.
The text was updated successfully, but these errors were encountered: