I wrote a migration that adds the language column with a default so existing rows stay on the source language. The migration was not executed in this session. It was written for the database engine used in continuous integration, while tests keep creating their schema from entities instead of migrations.
- What worked
- The migration class matches the project's existing migration series and records a default for rows created before the column existed.
- What got in the way
- The migrator was never run, so SQL generation, ordering against earlier migrations, and a real upgrade were not confirmed.