#35499: Issue with auto_now=True DateTimefield and update_fields
-------------------------------------+-------------------------------------
Reporter: Mohamed El-Kalioby | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* resolution: => duplicate
* status: new => closed
Comment:
[https://docs.djangoproject.com/en/5.0/ref/models/instances/#specifying-
which-fields-to-save This is documented] and has been discussed plenty
already. Please take [https://code.djangoproject.com/query a minute to
search the bug tracker] before filling a new report as pointed out in the
**Please read this first** [https://code.djangoproject.com/newticket
section]. Both `auto_now` and `update_fields` being options introduced in
Django more than 10 years ago it is very likely that someone else ran into
the same problem as you already. When in doubt
[https://code.djangoproject.com/newticket rely on support channels before
opening a ticket].
Duplicate of #22981 and #30319 which were both wont-fix'ed.
--
Ticket URL: <https://code.djangoproject.com/ticket/35499#comment:1>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018fed661341-035cdc5d-aa99-482d-b953-71c1fbbfaeba-000000%40eu-central-1.amazonses.com.
