#35957: Allow AutoFields in composite primary keys
-------------------------------------+-------------------------------------
Reporter: Csirmaz Bendegúz | Owner: (none)
Type: New feature | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"bfcb34076e3c0c04cb5080a37d93225444ac1b82" bfcb340]:
{{{#!CommitTicketReference repository=""
revision="bfcb34076e3c0c04cb5080a37d93225444ac1b82"
Refs #373 -- Removed unused composite pk code in SQLInsertCompiler.
This logic could only be exercised if the composite primary key included
an
AutoField but it's not allowed yet (refs #35957).
It was also slightly broken as it expected the AutoField to always be the
first
member of returning_fields.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35957#comment:6>
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/010701945f278c9a-f068ca04-f23a-4cc6-8186-6f2cbb11f052-000000%40eu-central-1.amazonses.com.
