Hi Aron, Short version - if you're eager to look into this, we're eager to have composite keys in Django - it's probably one of the last features I can think of that was discussed for the 1.0 release but we bumped so that "we can add it for 1.1".
(ahem. :-) Yes, there have been a lot of changes since Michal Petrucha (koniiik) last worked on his patch - most notably, migrations and the Meta refactor have landed. Both of these will have a big impact on any composite key design. However, there have also been a bunch of changes to the internals of ForeignKeys that will aid in the implementation of composite keys; the design of the meta refactor also kept the potential requirements of composite keys in mind. Michal's github branch is probably still the best place to start - he's done a lot of work on this project, and at the very least should be able to guide you as to what is left to be done. Best of luck! Yours, Russ Magee %-) On Tue, Feb 24, 2015 at 2:14 PM, Aron Podrigal <[email protected]> wrote: > Hi, I just came across a project that requires this functionality of > multi primary/foreign keys. So I'm bumping up this thread > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!searchin/django-developers/composite$20fied/django-developers/m8rO3Id5j-o/yV4H1w_2P9YJ>again. > There were a lot of changes in django and the db api hasre-factored since > this topic was discussed. It might be a time for another start on this > project. I'm willing to work on this as long it is ok with the core > developers. I didn't have much time yet to spend on this. I'm still reading > through the other earlier threads on possible implementations. > I will post my proposal for this over the weekend. In the meantime I would > like to get some feedback from the community. > > Aron. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" 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]. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/a4a31a7b-4759-4006-a280-34d9ac6b0abe%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/a4a31a7b-4759-4006-a280-34d9ac6b0abe%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq84_c2j%3D_gvHVdYxBq81SHKrx5-rLcpox1txSKkrDNtePhw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
