#28671: DateTimeField: make auto_now_add just a default value
-------------------------------------+-------------------------------------
Reporter: Дилян Палаузов | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => wontfix
* type: Uncategorized => Cleanup/optimization
Comment:
Is there a problem with using `default=date.today` or
`default=timezone.now` (as the documentation suggests) for your use case?
There's some thought to deprecate `auto_now` and `auto_now_add` (#22995),
and I don't see a compelling reason to change their behavior when an
alternative exists.
--
Ticket URL: <https://code.djangoproject.com/ticket/28671#comment:1>
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/072.44b45555370addc29ff8c2bd0ba1f973%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
