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
23405	Blank-able CharFields require default=''	Yuval Adam	Andriy Sokolovskiy	"There's a weird behavior in Django 1.7 migrations as opposed to 1.6 + South.

Consider a simple blank-able CharField:

{{{
comment = models.CharField(max_length=20, blank=True)
}}}

In Django 1.6 + South, adding a migration to add this field would auto-generate `default=''` in the migration. In Django 1.7 the migration now throws: ""You are trying to add a non-nullable field 'test' to question without a default"".

My understanding is that this is the proper convention for blank-able fields, and in that case the migrations need to support it properly.
"	Bug	closed	Migrations	1.7	Normal	fixed		Simon Charette Andriy Sokolovskiy	Accepted	1	0	0	1	0	0