#26239: Document auto_now behavior with QuerySet.update()
--------------------------------------+------------------------------------
Reporter: boussouira | Owner: duane9
Type: Cleanup/optimization | Status: assigned
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 duane9):
Replying to [comment:4 boussouira]:
I think the documentation already specifies this: "Automatically set the
field to now every time the object is saved."
https://docs.djangoproject.com/en/1.9/ref/models/fields/#django.db.models.DateField.auto_now
Does the documentation need something more?
> 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: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 [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/068.2084190469d89103af6860150a4eff5e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
