Explains schema migration and rollback
Changes to a populated database need migrations and backfills; dropping tables is not a rollback.
Can AI do this?
AI does this partly Some of the tested AI models master this; others do not show it. 3 of 10 models master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 100% | Mastered |
| gemini-3.1-pro-preview | Flagship | 75% | Not shown |
| gpt-6-astra | Flagship | 100% | Mastered |
| claude-fable-5-1 | Flagship | 76% | Not shown |
| gemini-3.8-flash | Mid tier | 75% | Not shown |
| gpt-6.1-sol | Mid tier | 100% | Mastered |
| claude-sonnet-5-5 | Mid tier | 76% | Not shown |
| gemini-3.5-flash-lite | Low cost | 76% | Not shown |
| gpt-6-luna | Low cost | 75% | Not shown |
| claude-haiku-5-5 | Low cost | 76% | Not shown |
Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.
What it looks like in practice
Expected result: Changes to a populated database need migrations and backfills; dropping tables is not a rollback
How it is assessed: Plans the migration and rollback for sample changes
Related knobits
Needed for
- K-822 Recognises greenfield DDL aimed at a populated database
- K-823 Recognises a drop script used as a rollback
All 33 knobits of Generate and review DDL.
Source: Data-management practice used by the stage 8 reference and review checklist