#14623: DateTimeField(auto_now=True) does not change when update is called
---------------------------------------------------+------------------------
Reporter: mklauber | Owner: nobody
Status: closed | Milestone: 1.3
Component: Database layer (models, ORM) | Version: 1.2
Resolution: invalid | Keywords:
DateTimeField auto_now
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by lukeplant):
* status: new => closed
* resolution: => invalid
Comment:
I really don't think that the docs for
[http://docs.djangoproject.com/en/dev/ref/models/querysets/#update-kwargs
update()] would give you the expectations you describe. It is very clear
that it works on the level of an SQL update and the save() method is not
called, and the docs for `DateTimeField` are equally clear that auto_now
is applied when the object is saved. Django has DB access code on several
levels, and we cannot add caveats for every single low level operation in
the docs for every single high level operation.
--
Ticket URL: <http://code.djangoproject.com/ticket/14623#comment:4>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
