#36075: Field.primary_key documentation should details its interaction with
CompositePrimaryKey
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
Type: | Charette
Cleanup/optimization | Status: closed
Component: Documentation | Version: dev
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
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"4bfec242b488b174f7d386ab5bbd3363751cdb93" 4bfec242]:
{{{#!CommitTicketReference repository=""
revision="4bfec242b488b174f7d386ab5bbd3363751cdb93"
Fixed #36093 -- Adjusted unique checks to account for inherited primary
keys.
Regression in bf7b17d16d3978b2e1cee4a0f7ce8840bd1a8dc4 refs #36075.
Thanks Sage Abdullah for the report and tests.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36075#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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701946567e132-fc6c3bc0-995f-4dfe-b5d1-0a1bd2381ecd-000000%40eu-central-1.amazonses.com.
