> > > But based on your traceback, it seems like at some point in the past > when you made a migration, the field might have had a default value > which was a naive datetime. Is that possible? > > It might be necessary to look through your existing migrations for this > app to find the culprit. > > Yes Carl you were right, I cleared out my migrations folder except for the "__init__.py" file and the problem went away.
-- 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 http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/c5bf130d-4715-4bf1-ba8a-5267f983ec7c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.