From de31423130912a012513aad93ec805f8e08a0d5e Mon Sep 17 00:00:00 2001 From: Benjamin Wohlwend Date: Wed, 23 Sep 2015 17:29:05 +0200 Subject: [PATCH] Fixed #25453 -- Reworded makemigration's ask_not_null_alteration suggestion. --- django/db/migrations/questioner.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/django/db/migrations/questioner.py b/django/db/migrations/questioner.py index a7e21969b5..aef80f4a52 100644 --- a/django/db/migrations/questioner.py +++ b/django/db/migrations/questioner.py @@ -148,8 +148,8 @@ class InteractiveMigrationQuestioner(MigrationQuestioner): [ "Provide a one-off default now (will be set on all existing rows)", ("Ignore for now, and let me handle existing rows with NULL myself " - "(e.g. adding a RunPython or RunSQL operation in the new migration " - "file before the AlterField operation)"), + "(e.g. because you added a RunPython or RunSQL operation to handle " + "NULL values in a previous data migration)"), "Quit, and let me add a default in models.py", ] )