id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
26075	Verbiage when using the makemigrations command with an interactive interpreter to remove null = True from a model field is misleading.	Mark McHenry	Susan Tan	"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 [https://github.com/django/django/blob/a7752780d9e78e12d0bd7bd2dcf920d304e039bc/django/db/backends/base/schema.py#L560 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""."	Cleanup/optimization	closed	Core (Management commands)	dev	Normal	fixed		markamodo@… susan.tan.fleckerl@…	Accepted	1	0	0	0	0	0