#23405: Blank-able CharFields require default=''
----------------------------+--------------------------------------
Reporter: yuvadm | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Comment (by andrewgodwin):
The original author is correct, CharFields are unique in their behaviour
that the empty value for new NOT NULL instances is assumed to "", much
like BooleanFields used to be False (but of course, that's the database
default anyway).
We should just modify the SchemaEditor to use "" as a default value if the
field is stringable and NOT NULL. I'm pretty sure most code to do this
already exists.
--
Ticket URL: <https://code.djangoproject.com/ticket/23405#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.a8940df643cbf9cd8f16038d10e89614%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
