Ticket #463 (closed enhancement: fixed)
CharField set to blank still requires default value
|Reported by:||btaylordesign@…||Owned by:||andrew|
To the best of my knowledge, it is not advisable to use null=True on CharFields?, but better use use an empty string.
When attempting to create a schemamigration on a CharField? specified as blank=True, South prompts me to either alter my model, or enter a one-time value for the field.
It seems as though South should treat blank=True the same as default= for CharFields?. I can't recall a single instance where I've ever specified default= on a CharField? in over two years of developing with Django.