#31947: QuerySet.update_or_create() should use get_or_create() internally
-------------------------------------+-------------------------------------
Reporter: homm | Owner: homm
Type: | Status: closed
Cleanup/optimization |
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:"20d38fd75903b58335abd8e7cc576a1f1219a4fa" 20d38fd7]:
{{{
#!CommitTicketReference repository=""
revision="20d38fd75903b58335abd8e7cc576a1f1219a4fa"
Fixed #31947 -- Made QuerySet.update_or_create() reuse get_or_create().
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31947#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.5b65f1c44662eba0de91779981918224%40djangoproject.com.
