diff options
| author | Mike Gunderloy <MikeG1@larkfarm.com> | 2008-11-09 12:54:27 -0600 |
|---|---|---|
| committer | Mike Gunderloy <MikeG1@larkfarm.com> | 2008-11-09 12:54:27 -0600 |
| commit | fb30b82bd0a0f2dc9974aea1fe2e32fb6d2b41a7 (patch) | |
| tree | 38058fcacde0e6ad6a7e08e9113ffcd9bbbe2e5b /railties/doc/guides/source | |
| parent | 3baa44ab00a2ca2c665a2631eb5880b4117effbd (diff) | |
| download | rails-fb30b82bd0a0f2dc9974aea1fe2e32fb6d2b41a7.tar.gz rails-fb30b82bd0a0f2dc9974aea1fe2e32fb6d2b41a7.tar.bz2 rails-fb30b82bd0a0f2dc9974aea1fe2e32fb6d2b41a7.zip | |
Mention DB2 Adapter transactional migration support in 2.2 relnotes.
Diffstat (limited to 'railties/doc/guides/source')
| -rw-r--r-- | railties/doc/guides/source/2_2_release_notes.txt | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/railties/doc/guides/source/2_2_release_notes.txt b/railties/doc/guides/source/2_2_release_notes.txt index ff285b85cd..c730f72748 100644 --- a/railties/doc/guides/source/2_2_release_notes.txt +++ b/railties/doc/guides/source/2_2_release_notes.txt @@ -118,11 +118,12 @@ There are two big additions to talk about here: transactional migrations and poo === Transactional Migrations -Historically, multiple-step Rails migrations have been a source of trouble. If something went wrong during a migration, everything before the error changed the database and everything after the error wasn't applied. Also, the migration version was stored as having been executed, which means that it couldn't be simply rerun by +rake db:migrate:redo+ after you fix the problem. Transactional migrations change this by wrapping migration steps in a DDL transaction, so that if any of them fail, the entire migration is undone. In Rails 2.2, transactional migrations are supported *on PostgreSQL only*. The code is extensible to other database types in the future. +Historically, multiple-step Rails migrations have been a source of trouble. If something went wrong during a migration, everything before the error changed the database and everything after the error wasn't applied. Also, the migration version was stored as having been executed, which means that it couldn't be simply rerun by +rake db:migrate:redo+ after you fix the problem. Transactional migrations change this by wrapping migration steps in a DDL transaction, so that if any of them fail, the entire migration is undone. In Rails 2.2, transactional migrations are supported on PostgreSQL out of the box. The code is extensible to other database types in the future - and IBM has already extended it to support the DB2 adapter. * Lead Contributor: link:http://adam.blog.heroku.com/[Adam Wiggins] * More information: - link:http://adam.blog.heroku.com/past/2008/9/3/ddl_transactions/[DDL Transactions] + - link:http://db2onrails.com/2008/11/08/a-major-milestone-for-db2-on-rails/[A major milestone for DB2 on Rails] === Connection Pooling |