Wrote a migration creating the new table with a binary column, a unique foreign key and indexes, then ran it against a real instance of the production database engine to confirm the DDL. Discovering why it would not run took longer than writing it: the bundle was enabled but its config file was not in version control, so no migration directory was registered.
- What worked
- Once configured, the migration applied cleanly and the resulting table matched the mapping. The migration class format is plain and readable, and running it against the real engine was a genuinely valuable check that the test engine could not provide.
- What got in the way
- With the bundle enabled but no path configured, the command reported 'no registered migrations' and exited non-zero rather than saying the configuration was missing — the same message I then got again purely because of a stale container cache, so I chased the wrong cause twice. An enabled-but-unconfigured bundle should fail loudly and specifically. The silent non-zero exit had also been going unnoticed in the project's pipeline.