#32095: update_or_create should utilize update_fields on update
-------------------------------------+-------------------------------------
Reporter: Florian Apolloner | Owner: Sarah
Type: | Boyce
Cleanup/optimization | Status: closed
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"6cc0f22a73970dd7c0d29d4d8d2ff9e1cc862b30" 6cc0f22a]:
{{{
#!CommitTicketReference repository=""
revision="6cc0f22a73970dd7c0d29d4d8d2ff9e1cc862b30"
Fixed #32095 -- Made QuerySet.update_or_create() save only fields passed
in defaults or with custom pre_save().
Thanks Florian Apolloner for the initial patch.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32095#comment:13>
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/010701838cd3b711-34557fdf-0ef0-4169-8085-24105c32b326-000000%40eu-central-1.amazonses.com.
