#26239: Document auto_now behavior with QuerySet.update()
--------------------------------------+------------------------------------
Reporter: boussouira | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by boussouira):
Hi, Sorry for delay in replay.
I think documentation change is better, so existing applications won't
have to do any changes to upgrade.
As i understand now, you must call `save()` for the auto-update field to
be populated, which is fine, but explicitly mentioning that in the
documentation good for new users (like me).
Thank you.
--
Ticket URL: <https://code.djangoproject.com/ticket/26239#comment:4>
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/068.d1e855be00654e2b21cbaee2b25d5012%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
