#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):

 I apologize for the lack of timely response.

 #19385 looks like it implements the last big piece that is missing from my
 work. I'll need to have a more thorough look at it though.

 The current status of my work is kinda sad. The repo is badly out of date
 because it has become a real pain to keep it in sync with master. I won't
 get into much detail about why here, but I think it isn't worth the effort
 to try to sync it up. Basically, the problem is that I first implemented
 `CompositeField` (in branch `soc2011/composite-fields`) without
 `ForeignKey` support and then I started to refactor `ForeignKey` on top of
 that (`auxiliary_fk_fields`). This has become a real nightmare to
 maintain. I managed to get the branches through the initial Py3k changes
 but that required carefully merging each upstream commit one by one, after
 that there were numerous cleanups in the ORM which I didn't get around to
 merging.

 However, that doesn't mean I'm giving up, I've got other plans. The idea
 is to do it the other way around, first refactor `ForeignKey` and only
 after it works with simple fields, port `CompositeField` on top of it.
 This should still make it possible to reuse most of the code I wrote
 throughout the past two years and make the changes easier to follow.

 I'd like to apply for the upcoming Google Summer of Code with this to
 finally put this to rest, so keep an eye out on django-developers@ for an
 email in the near future.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/373#comment:118>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to