From 2918927973323e4f7b6099e7cda43b892da312ac Mon Sep 17 00:00:00 2001 From: Paul McMahon Date: Mon, 24 Apr 2023 11:18:00 +0900 Subject: [PATCH] Reword to avoid ambiguity [ci-skip] As written, it wasn't clear if each migration was run in its own transaction, or all migrations are run in a single transaction. --- guides/source/active_record_migrations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/source/active_record_migrations.md b/guides/source/active_record_migrations.md index 03bbd15a511d1..31e09fd89d935 100644 --- a/guides/source/active_record_migrations.md +++ b/guides/source/active_record_migrations.md @@ -59,7 +59,7 @@ exist. Active Record knows how to reverse this migration as well: if we roll this migration back, it will remove the table. On databases that support transactions with statements that change the schema, -migrations are wrapped in a transaction. If the database does not support this +each migration is wrapped in a transaction. If the database does not support this then when a migration fails the parts of it that succeeded will not be rolled back. You will have to rollback the changes that were made by hand.