On Sat, Jun 10, 2017 at 5:03 AM, Melvyn Sopacua <m.r.sopa...@gmail.com> wrote:
> 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. > > I should have mentioned that I checked for empty date fields first and they were all populated. My work around was to skip the migration. Just redid the dependency on the next migration and all was well. Thanks. -- 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. 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/CA%2BePoMyD3_5o6p%2BwfJO%3DVa2L%2B__9vEQx6E-jg2BmCyGrawFQew%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
