Verbiage when using the makemigrations command with an interactive interpreter to remove null = True from a model field is misleading.

[Mark McHenry]

Verbiage when using the makemigrations command with an interactive interpreter to remove null from a model field is misleading.

I added null = True to foreignkey field and applied a migration. I want to revert the change and am being prompted during the second migration that a default must be provided for existing rows.

The first option for addressing this says to provide a one-off and then states, "will be set on all existing rows".

This verbiage indicates that existing values will be replaced with the one-off.

In reality, according to the Django source ​here, this will only apply the one-off value to rows which currently have a null value for this column.

I am filing this ticket to have the verbiage updated to more accurately reflect what will occur. My recommended replacement text is "will be set on all existing rows with a null value for this column".

[Susan Tan]

​https://github.com/django/django/pull/6398 is the PR. Is this what you're looking for?

[Markus Holtermann <info@…>]

In b0803d6:

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