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.

Sign up for GitHub

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

Jump to bottom

Implement schema migration #42

Open
mcflyhalf opened this issue Apr 2, 2021 · 0 comments
Open

Implement schema migration #42

mcflyhalf opened this issue Apr 2, 2021 · 0 comments
Labels
Back end Back end of the application enhancement New feature or request
Milestone
V4. Portfolio-worthy

Comments

@mcflyhalf
Copy link
Owner

Schema migration should happen (mostly) automatically when the schema changes without any loss of pre-existing data. Currently, during development all tables are dropped and re-populated with some default data from a script tests/populatedb.py
@mcflyhalf mcflyhalf added Back end Back end of the application enhancement New feature or request labels Apr 8, 2021
@mcflyhalf mcflyhalf added this to the V4. Portfolio-worthy milestone Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Back end Back end of the application enhancement New feature or request
Projects
None yet
Milestone
V4. Portfolio-worthy
Development

No branches or pull requests
1 participant
@mcflyhalf