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

[FEATURE] Database Migration Actions #322

Open
DMalone87 opened this issue Feb 11, 2024 · 0 comments
Open

[FEATURE] Database Migration Actions #322

DMalone87 opened this issue Feb 11, 2024 · 0 comments
Labels
backend enhancement New feature or request

Comments

@DMalone87
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
Currently, any changes made to the database models have a good chance of causing the code and database to become disconnected. This causes the API commands related to pulling data from the database to fail.

Describe the solution you'd like
To solve this problem will require two things:

  • Update the documentation with instructions on how to add database migrations to pull requests that cause changes to the database.
  • Add a step to our deploy actions that will run any migrations included in a pull request.

Describe alternatives you've considered
An alternative solution would be to adopt a database technology that doesn't require strict schemas.

Additional context
Our code currently includes Alembic, which is a library that handles migration actions.

@DMalone87 DMalone87 added enhancement New feature or request backend labels Mar 27, 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