#36074: Updating a model instance with a composite primary key through .save()
results in unnecessary re-assignment of primary key fields
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | 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 Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"af6336f2c82fd6e5a0e42a7650a3a132c3362a0f" af6336f]:
{{{#!CommitTicketReference repository=""
revision="af6336f2c82fd6e5a0e42a7650a3a132c3362a0f"
Fixed #36074 -- Excluded composite primary key fields on save() updates.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36074#comment:4>
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/010701944beec910-6ae1d349-71eb-40c6-b200-8c6347734f11-000000%40eu-central-1.amazonses.com.
