{"action":"created","issue":{"url":"https://api.github.com/repos/flyway/flyway/issues/181","labels_url":"https://api.github.com/repos/flyway/flyway/issues/181/labels{/name}","comments_url":"https://api.github.com/repos/flyway/flyway/issues/181/comments","events_url":"https://api.github.com/repos/flyway/flyway/issues/181/events","html_url":"https://github.com/flyway/flyway/issues/181","id":15970249,"number":181,"title":"Support Multiple Migrations within a single Transaction","user":{"login":"flyway","id":2109532,"avatar_url":"https://avatars.githubusercontent.com/u/2109532?v=3","gravatar_id":"","url":"https://api.github.com/users/flyway","html_url":"https://github.com/flyway","followers_url":"https://api.github.com/users/flyway/followers","following_url":"https://api.github.com/users/flyway/following{/other_user}","gists_url":"https://api.github.com/users/flyway/gists{/gist_id}","starred_url":"https://api.github.com/users/flyway/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/flyway/subscriptions","organizations_url":"https://api.github.com/users/flyway/orgs","repos_url":"https://api.github.com/users/flyway/repos","events_url":"https://api.github.com/users/flyway/events{/privacy}","received_events_url":"https://api.github.com/users/flyway/received_events","type":"Organization","site_admin":false},"labels":[{"url":"https://api.github.com/repos/flyway/flyway/labels/feature","name":"feature","color":"bfe5bf"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2013-06-25T10:06:08Z","updated_at":"2015-03-18T14:36:38Z","closed_at":null,"body":"_Original author: ke...@fidelma.com (April 24, 2013 05:01:42)_\n\nWhen upgrading a database I would expect all un-applied migrations to be applied within the same transaction. Currently each migration runs within its own transaction.\n\nMy use-case looks something like this:\n\n1. Version 1.0 is deployed into Production\n2. Developers work on features for Version 2.0, each creating a migration script matching their new feature.\n3. As development progresses, V2.x migrations, and the associated application, are put into QA.\n4. Eventually we decide we've done enough, and want to release v2, and it's myriad migration scripts.\n5. When we run the deployment against v1 in production we expect all the v2.x migrations to run, and if there is a problem with any of them, then the database is rolled back, and we revert the application to v1 while we figure out what went wrong. \n\nWe really don't want *some* of the v2 scripts to be committed to the production database.\n\nWe're using Postgres, so DDL rolls back nicely.\n\nI'm happy to do the change, if nobody else is interested, but it seems like an &quot;obvious&quot; feature to me. None of your competition seem to offer it either. Am I missing something?\n\n\n_Original issue: http://code.google.com/p/flyway/issues/detail?id=484_"},"comment":{"url":"https://api.github.com/repos/flyway/flyway/issues/comments/82998847","html_url":"https://github.com/flyway/flyway/issues/181#issuecomment-82998847","issue_url":"https://api.github.com/repos/flyway/flyway/issues/181","id":82998847,"user":{"login":"alexeev","id":93481,"avatar_url":"https://avatars.githubusercontent.com/u/93481?v=3","gravatar_id":"","url":"https://api.github.com/users/alexeev","html_url":"https://github.com/alexeev","followers_url":"https://api.github.com/users/alexeev/followers","following_url":"https://api.github.com/users/alexeev/following{/other_user}","gists_url":"https://api.github.com/users/alexeev/gists{/gist_id}","starred_url":"https://api.github.com/users/alexeev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alexeev/subscriptions","organizations_url":"https://api.github.com/users/alexeev/orgs","repos_url":"https://api.github.com/users/alexeev/repos","events_url":"https://api.github.com/users/alexeev/events{/privacy}","received_events_url":"https://api.github.com/users/alexeev/received_events","type":"User","site_admin":false},"created_at":"2015-03-18T14:36:38Z","updated_at":"2015-03-18T14:36:38Z","body":"+1\r\nI would appreciate this feature!"}}