#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 jeremyt):
Yeah.. the ideas on this have been plentiful as shown by that thread. The
optional primary_key Meta option definitely goes with the DRY principle
that Django is based upon but as long as the scenario is enabled, then I'm
ok with spelling it out every time.
This patch plus the work I've done on multi-column joins
[https://code.djangoproject.com/ticket/19385] should open up some major
use cases. I lend a helping hand to this issue, as well, to handle any
concerns.
--
Ticket URL: <https://code.djangoproject.com/ticket/373#comment:116>
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.
