diff options
author | Jason Noble <perlwizard@gmail.com> | 2011-12-03 19:03:26 -0700 |
---|---|---|
committer | Jason Noble <perlwizard@gmail.com> | 2011-12-03 19:31:43 -0700 |
commit | c8f8ecfd38e20ee936ea4ccbb879acf006fe3cb8 (patch) | |
tree | 138e5e9411f83b5b53f18392bbf2872938bb7fa1 /railties/guides/source | |
parent | 78f6672a43ac556c19f8d4c9a6645911daa3bd1c (diff) | |
download | rails-c8f8ecfd38e20ee936ea4ccbb879acf006fe3cb8.tar.gz rails-c8f8ecfd38e20ee936ea4ccbb879acf006fe3cb8.tar.bz2 rails-c8f8ecfd38e20ee936ea4ccbb879acf006fe3cb8.zip |
Rollback is used elsewhere in the tutorial
Diffstat (limited to 'railties/guides/source')
-rw-r--r-- | railties/guides/source/migrations.textile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/guides/source/migrations.textile b/railties/guides/source/migrations.textile index e6401a4bb7..ee0aa1d0f1 100644 --- a/railties/guides/source/migrations.textile +++ b/railties/guides/source/migrations.textile @@ -129,7 +129,7 @@ existing records (if necessary using your models). On databases that support transactions with statements that change the schema (such as PostgreSQL or SQLite3), migrations are wrapped in a transaction. If the database does not support this (for example MySQL) then when a migration fails -the parts of it that succeeded will not be rolled back. You will have to unpick +the parts of it that succeeded will not be rolled back. You will have to rollback the changes that were made by hand. h4. What's in a Name |