On Friday 09 June 2017 20:56:46 James Schneider wrote: > Quite honestly this sounds like a bug in the migration system if > that's the case. I'm pretty sure it should ask what value to use as a > filler value during the migration, although I haven't had a change > like that in a while.
When you *remove* a default, there is no need to migrate existing rows, as they have a default. -- Melvyn Sopacua -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2632657.8W4H3mhAj8%40devstation. For more options, visit https://groups.google.com/d/optout.
