#32095: update_or_create should utilize update_fields on update
-------------------------------------+-------------------------------------
Reporter: Florian Apolloner | Owner: Sarah
Type: | Boyce
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Normal | Resolution:
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
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"1d77b931f7df96ec4d6fa3835fe35547397cca1a" 1d77b93]:
{{{
#!CommitTicketReference repository=""
revision="1d77b931f7df96ec4d6fa3835fe35547397cca1a"
Refs #32095 -- Added model's Options._non_pk_concrete_field_names
property.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32095#comment:12>
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/010701838cd3b6a9-39cad86a-02ba-4737-acce-979f5e91d740-000000%40eu-central-1.amazonses.com.
