#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):
Well… The `Meta.primary_key` option was the first proposed API and the
outcome of [[https://groups.google.com/d/topic/django-
developers/Y0aAb792cTw/discussion|this discussion]] was that the BDFL
disliked this option and preferred an explicit `CompositeField`. The
arguments for either option were mostly a matter of personal preference,
therefore we settled on the one chosen by Jacob.
Personally, I don't really care. I can deliver the code for either one,
there's not that much of a difference as far as the implementation is
concerned. I'll start a thread on django-developers@ in the upcoming weeks
regarding the status of this project and my plans, that could be a good
opportunity for you to bring this up. Just keep in mind that this feature
has a history of attracting lots of bikeshedding discussions while the
more serious architectural issues are mostly being ignored. To me, this
smells more like the former. So, whatever the final decision on django-
developers@ is, I'll just accept it and write it that way.
--
Ticket URL: <https://code.djangoproject.com/ticket/373#comment:115>
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.