#36275: Update auto_now fields when using bulk_update
-------------------------------------+-------------------------------------
Reporter: Rodolfo Becerra | Owner: Rodolfo
| Becerra
Type: New feature | Status: closed
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: auto_now, | Triage Stage:
bulk_update | 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: => invalid
* status: assigned => closed
Comment:
For the same reasons `update` (#15566) and `update_or_create`
(ticket:35890#comment:6) don't implicitly cover `auto_now` fields in call
cases I wouldn't expect `bulk_update` do to so either.
Given there's an open ticket to deprecate `auto_now` #22995 altogether I'm
going to close this ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/36275#comment:2>
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 visit
https://groups.google.com/d/msgid/django-updates/01070195c977c972-c2432abf-e1b7-423d-aa31-f1081f6eb248-000000%40eu-central-1.amazonses.com.
