#373: Add support for multiple-column primary keys
-------------------------------------+-------------------------------------
Reporter: jacob | Owner: koniiiik
Type: New | Status: assigned
feature | Component: Database layer
Milestone: | (models, ORM)
Version: | Severity: Normal
Resolution: | Keywords: database
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Comment (by koniiiik):
Okay, a progress update:
there's a branch on github: https://github.com/koniiiik/django/
Currently, you can define a composite field, set it as the primary key and
basically that's it. No support in ForeignKey or any other relationship
fields yet, that's what I'll work on starting with the next week. Model
validation is missing as well, i. e. CompositeFields are not yet checked
for correctness.
The admin should just work, try to explore its functionality and please
let me know if you find something broken. I tried to test everything I saw
but of course, I may have forgotten about a few details.
All in all, feel free to clone the repo and try it out, any feedback I get
will push me forward.
--
Ticket URL: <https://code.djangoproject.com/ticket/373#comment:85>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
