85 1 true 2008-08-14T19:58:53+01:00 17515 9903 834 make-migrations-use-transaction-and-rollback-if-something-was-wrong 291 8994 resolved activerecord migrations 2008-08-22T22:47:01+01:00 17393 Repository Ian Bailey Jeremy Kemper http://rails.lighthouseapp.com/projects/8994/tickets/834 2.x When a migration is running and an error is raised, everything before the error is applied to the database schema and everything before (obviously) doesn't. Also, the migration version is stored as executed, which creates schema inconsistency and migration version control brokeness. This would not work for migrations involving schema changes on databases that do not support DDL rollback (i.e. MySQL, Oracle). This ticket was in "Trac ticket 5470":http://dev.rubyonrails.org/ticket/5470 but was not resovled. There are working patches on that ticket. When a migration is running and an error is raised, everything before the error is applied to the database schema and everything before (obviously) doesn't. Also, the migration version is stored as executed, which creates schema inconsistency and migration version control brokeness. This would not work for migrations involving schema changes on databases that do not support DDL rollback (i.e. MySQL, Oracle). This ticket was in "Trac ticket 5470":http://dev.rubyonrails.org/ticket/5470 but was not resovled. There are working patches on that ticket. <div><p>When a migration is running and an error is raised, everything before the error is applied to the database schema and everything before (obviously) doesn't. Also, the migration version is stored as executed, which creates schema inconsistency and migration version control brokeness.</p> <p>This would not work for migrations involving schema changes on databases that do not support DDL rollback (i.e. MySQL, Oracle).</p> <p>This ticket was in <a href="http://dev.rubyonrails.org/ticket/5470">Trac ticket 5470</a> but was not resovled. There are working patches on that ticket.</p></div> 0 When a migration is running and an error is raised, everything before the error is applied to the database schema and everything before (obviously) doesn't. Also, the migration version is stored as executed, which creates schema inconsistency and migration version control brokeness. This would not work for migrations involving schema changes on databases that do not support DDL rollback (i.e. MySQL, Oracle). This ticket was in "Trac ticket 5470":http://dev.rubyonrails.org/ticket/5470 but was not resovled. There are working patches on that ticket. <div><p>When a migration is running and an error is raised, everything before the error is applied to the database schema and everything before (obviously) doesn't. Also, the migration version is stored as executed, which creates schema inconsistency and migration version control brokeness.</p> <p>This would not work for migrations involving schema changes on databases that do not support DDL rollback (i.e. MySQL, Oracle).</p> <p>This ticket was in <a href="http://dev.rubyonrails.org/ticket/5470">Trac ticket 5470</a> but was not resovled. There are working patches on that ticket.</p></div> false 2008-08-14T19:58:53+01:00 17515 --- {} 9903 834 make-migrations-use-transaction-and-rollback-if-something-was-wrong 0 8994 new activerecord migrations 2008-08-14T19:58:53+01:00 17515 Ian Bailey Ian Bailey http://rails.lighthouseapp.com/projects/8994/tickets/834 2.x 1 Rebased the patch from trac and added a test. <div><p>Rebased the patch from trac and added a test.</p></div> false 2008-08-22T22:03:07+01:00 17515 --- {} 9903 834 make-migrations-use-transaction-and-rollback-if-something-was-wrong 0 8994 new activerecord migrations 2008-08-22T22:03:07+01:00 14890 Tarmo Tänav Ian Bailey http://rails.lighthouseapp.com/projects/8994/tickets/834 2.x 85 1 false 2008-08-22T22:19:15+01:00 17515 --- :assigned_user: 9903 834 make-migrations-use-transaction-and-rollback-if-something-was-wrong 0 8994 new activerecord migrations 2008-08-22T22:19:15+01:00 14890 Tarmo Tänav Ian Bailey Jeremy Kemper http://rails.lighthouseapp.com/projects/8994/tickets/834 2.x 85 1 (from [707ee0e2695e85186d59aa407f09691ebfcc3125]) Made migrations transactional for PostgreSQL [#834 state:resolved] Patch originally from http://dev.rubyonrails.org/ticket/5470 http://github.com/rails/rails/commit/707ee0e2695e85186d59aa407f09691ebfcc3125 <div><p>(from [707ee0e2695e85186d59aa407f09691ebfcc3125]) Made migrations transactional for PostgreSQL [<a href="/projects/8994/tickets/834" title="Ticket #834">#834</a> state:resolved]</p> <p>Patch originally from <a href="http://dev.rubyonrails.org/ticket/5470">http://dev.rubyonrails.org/ticke...</a> <a href="http://github.com/rails/rails/commit/707ee0e2695e85186d59aa407f09691ebfcc3125">http://github.com/rails/rails/co...</a></p></div> true 2008-08-22T22:47:00+01:00 17515 --- :state: new 9903 834 make-migrations-use-transaction-and-rollback-if-something-was-wrong 0 8994 resolved activerecord migrations 2008-08-22T22:47:00+01:00 17393 Repository Ian Bailey Jeremy Kemper http://rails.lighthouseapp.com/projects/8994/tickets/834 2.x 866b8961c7d634e753e80091bdbf5ed48dc473f2 text/plain 2008-08-22T22:03:06+01:00 0001-Made-migrations-transactional-for-PostgreSQL-834-s.patch 41029 5835 14890 http://rails.lighthouseapp.com/attachments/41029/0001-Made-migrations-transactional-for-PostgreSQL-834-s.patch