Kamus AI
Database migration
A numbered script that changes a database schema step by step, run in the same order in every environment.
A migration adds or changes tables, columns, indexes or access rules through numbered files that run in order and are recorded. A safe migration is additive (it adds, it does not remove) and can be re-run without damage. Rehearse a risky migration first on a schema-only copy of production, and run it before the app version that needs it starts serving.
Also called: Database migration, migration, schema migration
Related terms
Appears in 21 lessons
- Code from AI is a draft, and you own it
- A written plan before code: plan, build, review
- Prompts for plans and specifications
- Prompts for review, migrations and releases
- A release with a rehearsal and a way back
- Ready-to-use developer template pack
- Asking for small changes
- Data and migrations
- Project: a small team tool
- Your first release to a server
- Project: release the team tool to a server
- Plan, build, review
- Reviewers that test real data
- The real build as the gate
- Project: one real feature with tests
- Runbooks and checklists
- Final project: a complete app for real users
- Session 2: spec and written plan
- Session 4: release with a runbook and a rollback drill
- A staged release with a flag
- A human gate before release