#22995: Deprecate auto_now and auto_now_add and document alternatives
-------------------------------------+-------------------------------------
Reporter: jezdez | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.6
Component: Database layer | Resolution:
(models, ORM) | Triage Stage:
Severity: Normal | Unreviewed
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by kmtracey):
Doesn't the POC replace an auto_now flag w/ a save override that is
implementing auto_add_now? Which possibly does not matter since admin log
entries are generally not editable...?
What are the unexpected behaviors that can be fixed by replacing with
default/override save()? Or is it just more clear what the behavior will
be?
--
Ticket URL: <https://code.djangoproject.com/ticket/22995#comment:6>
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/064.30ea3c81e18f9f5c964033d654f39c45%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
