On Sat, Sep 4, 2010 at 7:17 AM, Brendon <brendon.j.co...@gmail.com> wrote: > I have a project where we have an existing database which uses > composite (multiple) primary keys for some of the tables. I want to > move everything over from PHP into DJango without changing the DB. > Reading the DJango docs though, it seems composite primary keys are > not supported. I looked online and found that someone was working on > this, but just noticed then that the ticket was closed and marked as > "wontfix". > > http://code.djangoproject.com/ticket/373
You must be looking at a different page to me, because this ticket is open and marked "accepted and assigned" when i look at it. > Can anyone tell me for sure if this support has been abandoned or at > least any information on the status of this? > > I wasn't sure if this was the best place to ask or django-developers. > Please let me know i should move this question over. Mutli-column composite keys are not currently supported by Django. Adding support for multi-column keys (primary or otherwise) is something that has been long discussed, and there is agreement that it is a desirable feature -- which is why the ticket is marked accepted. What is missing is someone to actually do the work. It's easy to get a basic implementation working, but there are a lot of nasty edge cases in admin and general usage that need to be resolved. Nothing is going to get committed to trunk until these issues have been sorted out. To the best of my knowledge, nobody is actively working on this at the moment. If you're interested in contributing, django-developers is the place to put forward your ideas and plans. Yours Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
