override default templates

[gflarity]

Hi,

Love this module!

Question: Is there way to override the default templates used for migrations?

We use postgres and always include a begin and commit statement in our migrations. Just want to add it to the default.

Thanks

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/8395534-override-default-templates?utm_campaign=plugin&utm_content=tracker%2F73887&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F73887&utm_medium=issues&utm_source=github).

[wzrdtales]

You can open a pull request adding new templates.

However, I'm looking into introduce a per migration transaction by default. So if a single migration fails everything gets rolled back and migration process stops right there.

Yet this is not within the scope of v0.9.0, but I always appreciate pull request ;)

[wzrdtales]

Related to #216

[AdriVanHoudt]

Would it be an option to do require('db-migrate/lib/migration') and override the prototypes?

[wzrdtales]

No, but we look to extend db-migrate to support real templates for migrations and make them extensible.

[wzrdtales]

Btw. the question raised at the beginning also included they want to use this to enforce the usage of transactions. Actually db-migrate always place a transaction begin and commit before and after every migration.

[wzrdtales]

closed in favour of #514