Using Phing's dbdeploy task with transactions
- by Gordon
I am using Phing's dbdeploy task to manage my database schema. This is working fine, as long as there is no errors in my delta file.
However, if there is an error, dbdeploy will just run the delta files up to the query with the error and then abort. This causes me some frustration, because I have to manually rollback the entry in the changelog table then. If I don't, dbdeploy will assume the migration was successful on a subsequent try.
So the question is, there any way to get dbdeploy use transactions?