#21785: migrate fails on DateTimeField with auto_now AND auto_now_add set
---------------------------------+----------------------------------------
Reporter: gabejackson | Owner: andrewgodwin
Type: Bug | Status: assigned
Component: Migrations | Version: master
Severity: Release blocker | Resolution:
Keywords: migrations | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
---------------------------------+----------------------------------------
Comment (by gabejackson):
for my defense... this was an autocomplete mistake i made in pycharm. Of
course it doesn't make sense to define both auto_now and auto_now_add, but
this should be caught when initializing the field.
--
Ticket URL: <https://code.djangoproject.com/ticket/21785#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.d78053c57412e622cebb10bd0a1d3d76%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
