#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 skizzay):
Jeremy makes a good point about placing primary_key as a constraint within
Meta. However, for the interest of time IMO, sticking with the current
plan is the best path. Adding primary_key to Meta later as an
afterthought (assuming the rest of the community finds a need for it)
should be simple enough without breaking (future) existing code.
What is the difference between the auxillary_fk_fields and soc2011
/composite-fields branches? How often is master merged? Obviously, this
isn't a simple change. Maybe the community could help out a little if
they had some status of what they could do to help.
--
Ticket URL: <https://code.djangoproject.com/ticket/373#comment:117>
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.
