#25005: DateField, DateTimeField defaults needed even when auto_now=True
-------------------------------------+-------------------------------------
Reporter: monobotsoft | Owner: yakky
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: DateField, | Triage Stage: Accepted
DateTimeField, TimeField |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"49c57f8565d4b655de5161d299a053eddfc00bf2" 49c57f85]:
{{{
#!CommitTicketReference repository=""
revision="49c57f8565d4b655de5161d299a053eddfc00bf2"
Fixed #25005 -- Made date and time fields with auto_now/auto_now_add use
effective default.
Thanks to Andriy Sokolovskiy for initial patch.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25005#comment:13>
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.d7057fc0abc327fb5b647edec96a0116%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
