When a migration tool is part of a larger deployment process it usually makes more sense to do the dependency analysis once and create a single migration file to be applied to the production database. The other benefit here is that the migration tool doesn't need to run in the production environments just on the build machine. (You won't need to install dependencies just for the migration tool everywhere).
Basically something like:
goose [options] sql > release_2012_03_06.sql
Would output all the SQL that needs to be run to migrate the database to the latest version.
When a migration tool is part of a larger deployment process it usually makes more sense to do the dependency analysis once and create a single migration file to be applied to the production database. The other benefit here is that the migration tool doesn't need to run in the production environments just on the build machine. (You won't need to install dependencies just for the migration tool everywhere).
Basically something like:
goose [options] sql > release_2012_03_06.sql
Would output all the SQL that needs to be run to migrate the database to the latest version.