#36075: Field.primary_key documentation should details its interaction with
CompositePrimaryKey
--------------------------------------+------------------------------------
Reporter: Simon Charette | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: dev
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Sarah Boyce):
* cc: Csirmaz Bendegúz (added)
Comment:
From #36074
> If you grep for .primary_key you'll notice that most of the checks
against this field need to be adjusted to use field in opts.pk_fields
instead which makes me wonder if we took the right decision by not setting
this flag to True when included as a member of CompositePrimaryKey.
--
Ticket URL: <https://code.djangoproject.com/ticket/36075#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 visit
https://groups.google.com/d/msgid/django-updates/0107019449fed217-73ef4611-8d9e-4a57-9f7e-1cd51842145b-000000%40eu-central-1.amazonses.com.
