From c8f8ecfd38e20ee936ea4ccbb879acf006fe3cb8 Mon Sep 17 00:00:00 2001 From: Jason Noble Date: Sat, 3 Dec 2011 19:03:26 -0700 Subject: Rollback is used elsewhere in the tutorial --- railties/guides/source/migrations.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'railties/guides/source') 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 -- cgit v1.2.3