#36070: clean_fields(exclude=["pk"]) not implemented for composite primary keys
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jacob
Type: | Walls
Cleanup/optimization | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | 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 Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"f054045973ea767ee4e3d60723de4a2f13bf0c49" f0540459]:
{{{#!CommitTicketReference repository=""
revision="f054045973ea767ee4e3d60723de4a2f13bf0c49"
Refs #36070 -- Referred to pk as an attribute when a composite primary key
is defined.
This is to avoid confusion that a field is often associated with having
a single associated database column.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36070#comment:11>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019469fe6878-c1ae99c1-32fc-475e-a06c-d0aef281e606-000000%40eu-central-1.amazonses.com.
