Open mtreacy002 opened 3 years ago
Merging #1133 (21ec10c) into develop (d717c93) will not change coverage. The diff coverage is
100.00%
.:exclamation: Current head 21ec10c differs from pull request most recent head d0acedd. Consider uploading reports for the commit d0acedd to get more accurate results
@@ Coverage Diff @@
## develop #1133 +/- ##
========================================
Coverage 92.95% 92.95%
========================================
Files 38 38
Lines 2073 2073
========================================
Hits 1927 1927
Misses 146 146
Impacted Files | Coverage Δ | |
---|---|---|
run.py | 96.15% <100.00%> (ø) |
@isabelcosta, @epicadk, @vj-codes, this PR is now ready for a review. Look forward to your feedback 😉.
Description
Initiate migration script and add running migration script to README
Fixes #996
Type of Change:
Code/Quality Assurance Only
How Has This Been Tested?
migrations > versions
folder before running initial migrationafter running initial migration
The local db will be updated one version at a time accordingly from initial to second revision
from second to third revision
When you are making changes by adding attribute/s to an existing db model
When you are making changes by ALTERING EXISTING ATTRIBUTES inside an existing db model Example case: User table Changes:
name
tofull_name
IMPORTANT Noticed that the auto-generated alembic script IS NOT CORRECT!!. You MUST MODIFY the script to reflect the intended schema changes. Once you're done, you can run
flask db upgrade
before alteration
After alteration (with data successfully preserved)
Checklist:
Code/Quality Assurance Only
ADDITIONAL NOTE NA