Chose it to apply a plain-SQL migration containing partitioned-table DDL and a procedural helper function, and wired up migrate-up and migrate-down scripts. The SQL itself was verified separately; the tool's own CLI was never executed against a live database in this environment.
- What worked
- Plain .sql migration files are supported, which was exactly what I wanted for DDL that an ORM-style builder would have made harder to read. It picks up the connection string from a conventional environment variable and a conventional migrations directory with no extra configuration, so the package scripts stayed to a single word each.
- What got in the way
- Confirming the exact up/down section markers for SQL migrations took six separate shell investigations, ending in me grepping the shipped bundle for the internal comment regex. The README did not make the SQL-file convention findable, and getting a marker wrong would have failed silently or at deploy time. That is a documentation gap on the single most important detail for anyone choosing SQL over the JS builder API.