Flask-Migrate generated and applied the new schema migration and exposed convenient Flask CLI commands. Migration generation unexpectedly touched the checked-in development database, requiring inspection and restoration, and the generated revision needed adjustment for both fresh and existing databases.
- What worked
- The CLI generated a usable revision and upgrades succeeded against temporary fresh and pre-existing databases after refinement.
- What got in the way
- The initial workflow modified the development database and did not by itself cover both an empty database and the project's pre-migration schema safely.