From f847aeb6f88b2a39d32a916b0649330764dc145e Mon Sep 17 00:00:00 2001 From: Moayad Mardini Date: Mon, 24 Mar 2014 13:06:39 +0200 Subject: [PATCH] [1.7.x] Fixed #22265 -- Clarfied consistent behavior of migrations. Thanks aruseni for the report. Backport of bff77e2aa8 from master --- docs/topics/migrations.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt index 5d7f9ac5e1..6904916c12 100644 --- a/docs/topics/migrations.txt +++ b/docs/topics/migrations.txt @@ -55,9 +55,9 @@ staging machines, and eventually your production machines. It is possible to override the name of the package which contains the migrations on a per-app basis by modifying the :setting:`MIGRATION_MODULES` setting. -Migrations will run the same way every time and produce consistent results, -meaning that what you see in development and staging is exactly what will -happen in production - no unexpected surprises. +Migrations will run the same way on the same dataset and produce consistent +results, meaning that what you see in development and staging is, under the +same circumstances, exactly what will happen in production. Backend Support ---------------