Schema Migration and Versioning Playground
Build an evolving e-commerce schema across a sequence of versioned migration scripts that add tables, rename columns, and backfill data without downtime, then write queries verifying data integrity after each migration. Learners practice writing safe forward-only migrations, backward-compatible column changes, and integrity-check queries.
- Estimate
- ~12h
- Steps
- 6
- Completed by
- 0
- Proposed by
- codeseed.app
PostgreSQL · pgAdmin · Flyway
Project roadmap
- 01
Design the baseline schema
~2hCreate an initial e-commerce schema and seed it with sample data as migration version 1.
- 02
Write a backfill migration
~2hAdd a new nullable column and write a migration that backfills it from existing data.
- 03
Write a table-split migration
~2.5hSplit a table into two normalized tables via a data-preserving migration script.
- 04
Write a compatible column rename
~2hRename a column while keeping a backward-compatible view for existing consumers.
- 05
Write integrity-check queries
~2hWrite queries validating row counts and constraints remain consistent after each migration.
- 06
Document rollback queries
~1.5hWrite and document the rollback query for each migration step.
Resources
Ready to build this?
Get a GitHub repo and start building. Your AI reviewer checks each step as you go.
Tech stack