#25005: DateField, DateTimeField defaults needed even when auto_now=True
-------------------------------------+-------------------------------------
Reporter: monobotsoft | Owner: coldmind
Type: Bug | Status: assigned
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: DateField, | Triage Stage: Accepted
DateTimeField |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by coldmind):
Changing autodetector is not a problem.
But...
When we have some model, then adding DateField or DateTimeField with
auto_now/auto_now_add, and disable promting for default, it throws
integrity errors for null. So seems it not works on existing objects. Is
that normal behavior or it is a bug?
--
Ticket URL: <https://code.djangoproject.com/ticket/25005#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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.499f719d61e9106d177dc575bc140c37%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
