On Friday 09 June 2017 18:08:39 Lee Hinde wrote: > I'm having problems with a migration after cleaning up an oddity with > a date field and I'm not sure how to fix it. Any advice appreciated. > > I made this change to a date field: > > - start_date = models.DateField(db_index=True, default=False, > - help_text="The date enrollment can > begin this Season.")
Apparently, this goes through, even though it's not a valid default for a date field (tested with 1.11.2). So that is the bug in the migrations system. Is it possible for you to rollback to before this migration or has this hit production already? -- 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 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/2731703.p1WpDnL8U3%40devstation. For more options, visit https://groups.google.com/d/optout.
