Skip to content
New issue

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

Consider using alembic for database migration #108

Open
lkeegan opened this issue Oct 15, 2024 · 0 comments
Open

Consider using alembic for database migration #108

lkeegan opened this issue Oct 15, 2024 · 0 comments
Labels
backend enhancement New feature or request

Comments

@lkeegan
Copy link
Member

lkeegan commented Oct 15, 2024

Once we have data in the database that we don't want to lose, if we need to modify the database schema then we need to migrate the data to the new schema.

For simple changes during development it is probably simplest to just directly modify the database accordingly.

But if this has to be done in production, a common way to do this is using alembic:

https://alembic.sqlalchemy.org/en/latest/

@lkeegan lkeegan added enhancement New feature or request backend labels Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant