#373: Add support for multiple-column primary keys
-------------------------------------+-------------------------------------
Reporter: jacob | Owner: koniiiik
Type: New feature | Status: assigned
Component: Database layer | Version:
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: database | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by koniiiik):
Adding a `primary_key` option to `Meta` would be redundant, both the
current API for single-column PKs and the proposed API for composite PKs
use the `primary_key` boolean flag on a `Field` instance. And as far as I
understand, attempts to add a new `Meta` option are usually turned down by
the core team (similar to project-level settings). However, if you have
good arguments, feel free to state them and this may still be considered.
As far as the progress goes, there is no timeline. The work is stalled
once again for lack of time (school and other projects requiring immediate
attention) but if the core team agrees, I'd like to take this to the final
stages this summer as part of GSoC.
--
Ticket URL: <https://code.djangoproject.com/ticket/373#comment:113>
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 post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
