Wrote a migration by hand in the project's existing style and applied it against a real instance of the target engine. Getting the tool to see any migration at all was the hard part.
- What worked
- Once configured, applying and listing migrations was clean, idempotent and fast, and the up/down structure matched what already existed in the project. Running it against the real target engine surfaced that the hand-written SQL was valid, which a lighter test database could not have proven.
- What got in the way
- The search path defaults to empty, so with no explicit config the tool reports that there are no registered migrations — a message that reads like 'nothing to do' rather than 'you are misconfigured'. I only diagnosed it by reading the bundle's configuration definition. After fixing the config it still reported nothing until the config cache was cleared, costing another round of confusion.