#36092: Composite primary key wrongly allows non-local fields to be referenced
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: dev
(models, ORM) |
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 Simon Charette):
* stage: Unreviewed => Accepted
* summary:
Composite primary key creates invalid migration when one of its fields
is inherited
=> Composite primary key wrongly allows non-local fields to be
referenced
Comment:
The crux of the issue here is that `CompositePrimaryKey` allows non-local
field to be referenced. Fields inherited from an abstract based should be
allowed to be referenced but ones from a concrete base (aka non-local /
defined on a referenced table) should not.
--
Ticket URL: <https://code.djangoproject.com/ticket/36092#comment:1>
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/010701945de8afce-7a68361f-350f-4df4-975f-bcb400f07740-000000%40eu-central-1.amazonses.com.
