#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
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* cc: Simon Charette, Lily Foote (added)
Comment:
Thank you Ben for clarifying. This seems to be outside what we discussed
in the forum. Do you have more resources to point me to understand the
bigger picture? I was assuming that our agreement and path forward with
`AutoField`s was described in the referenced forum post but before
proceeding I would like to have the full context.
--
Ticket URL: <https://code.djangoproject.com/ticket/35957#comment:3>
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/010701938cf31da6-cc168678-0e17-4427-88a7-9b5b33fdef52-000000%40eu-central-1.amazonses.com.
