#22981: Fields with auto_now=True are not updated if the field name is not
present
in update_fields list passed into Model.save
-------------------------------------+-------------------------------------
Reporter: jscn | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.6
(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
-------------------------------------+-------------------------------------
Comment (by npinchot):
Replying to [comment:4 timgraham]:
> Is there a problem with the suggestion of using a database default for
your use case? I don't think more "auto" options are desired considering
there has been some though to deprecate them (#22995).
Forgive my ignorance if I'm wrong, but my understanding is a database
default won't mimic 'auto_now' behavior since it would only default on
INSERT and won't change the value on UPDATE. It seems I would need a
trigger to mimic the 'auto_now' behavior. I know MySQL also has a
timestamp column type, but my understanding is this isn't the same as a
datetime and won't work the same.
--
Ticket URL: <https://code.djangoproject.com/ticket/22981#comment:5>
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/062.f87c4023f90d618a0917c1f863d9a4da%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
