Using migrations and fixtures
summary
Uses Symfony and Doctrine to codify schema changes as timestamped migration files and load small, meaningful datasets instead of multi‑GB dumps. Shows Doctrine migrations tied to Postgres, the risk of platform-specific SQL, the habit of deploying migrations before features instead of rolling back, and Laravel’s separate DSL for migrations. Demonstrates fixture references (e.g., PHP Day 2019 Verona conference) and a Makefile that drops, migrates and loads fixtures in seconds for repeatable local setups.
AI-written summary · about
chapters (17)
- 0:00Intro
- 2:40Migrations
- 4:30Doctrine
- 6:00Running migrations
- 7:40Never roll back
- 11:50Deploying migrations
- 13:00Deploying large datasets
- 14:20Starting from scratch
- 15:35Fixtures
- 17:30Communication
- 18:40Prayer
- 19:40Using migrations
- 24:10Makefile
- 25:25Fixture
- 27:33Adding a conference
- 29:43Adding city fixtures
- 31:17Adding city and conference fixtures
related talks
43mHow to avoid database migration hell
37mDatabase Schema Migrations with Zero Downtime
37mZero Downtime Database Migrations and Deployments
57mEating spaghetti with Symfony
59mHow much database abstraction do I need?
21mLaravel Doctrine: A Data Mapper Approach
21mDjango's Migrations: A Retrospective
36mUp And Down Again: A Migration's Tale