p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #26075 -- Added clearer wording for one-off values in makemigrations

This commit is contained in:
Susan Tan 2016-04-03 15:34:15 +02:00 committed by Markus Holtermann
parent b28c60529b
commit b0803d64c4
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
django/db/migrations/questioner.py
View File

@ -130,7 +130,8 @@ class InteractiveMigrationQuestioner(MigrationQuestioner):
"we can't do that (the database needs something to populate existing rows).\n" "we can't do that (the database needs something to populate existing rows).\n"
"Please select a fix:" % (field_name, model_name), "Please select a fix:" % (field_name, model_name),
[ [
"Provide a one-off default now (will be set on all existing rows)", ("Provide a one-off default now (will be set on all existing "
"rows with a null value for this column)"),
"Quit, and let me add a default in models.py", "Quit, and let me add a default in models.py",
] ]
) )
@ -149,7 +150,8 @@ class InteractiveMigrationQuestioner(MigrationQuestioner):
"populate existing rows).\n" "populate existing rows).\n"
"Please select a fix:" % (field_name, model_name), "Please select a fix:" % (field_name, model_name),
[ [
"Provide a one-off default now (will be set on all existing rows)", ("Provide a one-off default now (will be set on all existing "
"rows with a null value for this column)"),
("Ignore for now, and let me handle existing rows with NULL myself " ("Ignore for now, and let me handle existing rows with NULL myself "
"(e.g. because you added a RunPython or RunSQL operation to handle " "(e.g. because you added a RunPython or RunSQL operation to handle "
"NULL values in a previous data migration)"), "NULL values in a previous data migration)"),