#35014: update_or_create using update_fields opt out
-----------------------------------------+------------------------
Reporter: JordanHyatt | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 4.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
Prior to 4.2 update_or_create method did not use update_fields. That
means developer's could count on the model save method being run and all
fields being updated regardless of the defaults argument. After 4.2 only
those fields passed to default will be updated. This presents a major
breaking change especially for developers who rely heavily on save methods
to populate fields. I believe there should be a parameter added to
update_or_create that allows the user to opt out of using update_fields
during save.
--
Ticket URL: <https://code.djangoproject.com/ticket/35014>
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/0107018c3ab2f30e-f387581e-0e94-488c-be25-2d0d1cebc779-000000%40eu-central-1.amazonses.com.
