#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 yuvadm):
Replying to [comment:3 charettes]:
> I might not want the existing rows of the altered table to be equals to
`''` but a totally different value (e.g. `'active'`) even if it's not an
explicit `default` value used by the application.
>
> I think Django should continue to prompt the user instead of guessing
like South did.
This happens even for new fields being added. I would argue that any
existing field change is a data migration anyway, and requires manual
intervention.
In any case, my complaint pertains to new fields being introduced, and in
which case `default=''` is alread assumed by Django in any other aspect.
So why not in this aspect as well?
--
Ticket URL: <https://code.djangoproject.com/ticket/23405#comment:4>
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.65d7f5231b3e7823f4444729a381a840%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
