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
29848	If using db_column in a model makemigrations is wrong	Erik Bent	nobody	"I have the following line in a model:
    examplefield = models.CharField(db_column='ExampleField', max_length=75)

I changed the line into:
    example_field = models.CharField(db_column='ExampleField', max_length=75)

If I run makemigrations the following is asked:
Did you rename boek.examplefield to boek.example_field (a CharField)? [y/N] 

If I answer N there is an add column recorded in the migration file.
If I answer Y there is a rename from examplefield to example_field recorded in the migration file.

Both are wrong because there is an db_column in the CharField. The expected behavior is that the fIeld is not changed."	Bug	closed	Database layer (models, ORM)	2.1	Normal	invalid	migration		Unreviewed	0	0	0	0	0	0