If blank=False, then a new column with a non-blank value means that all existing objects won't pass form validation. Therefore, I don't see why a prompt for a value isn't helpful.
On Friday, September 9, 2016 at 6:42:02 AM UTC-4, Jarek Glowacki wrote: > > I made a rant/ticket regarding the hidden usage of `blank` here: #27197 > <https://code.djangoproject.com/ticket/27197#ticket>. > > In short, I don't think that `blank` should dictate whether or not the > migration questioner runs. > Building on this, I don't think it should run for for string-type fields > at all. If they have `default` set, use that for existing rows. Else if > they have `null=True`, set existing rows to `NULL`. Else, set existing rows > to empty string. > > See linked rant/ticket for some (hopefully) compelling arguments.. > > Thoughts? > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/aa6b4b3a-cc82-410d-99e5-066655daba77%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
