On Wed, Jul 21, 2010 at 9:18 PM, Rory Hart <hart...@gmail.com> wrote: > Hey Folks, > Just wondering if anyone had been squirreling away on the composite primary > key support that David Cramer and others were working on. It doesn't appear > any commits have been made on the git for almost a year and a half so I'm > wondering if anyone is still working on it. I'm happy to put my shoulder to > the wheel myself but just trying to get a lay of the land first. I've been > working on a project for the past 6 months that integrates with a legacy > database which contains loads of composite (foreign) primary keys. I have a > monster I keep in the basement that has allowed us to integrate > successfully, with some major annoyances (no admin for a lot of the project, > hand written create table SQL and no automatic south migrations for a > start). I'd love to be able to work towards putting the monster down as it > would make life easier for the team (and I'm sure there are others that > would love to see support for this too).
I can't speak for everybody who might be working on this in private, but I'm not aware of anyone who has made a public statement that they're working on this feature. Support for composite keys is certainly something I'd like to see in trunk. It's just waiting on someone to attack the problem and provide a complete solution -- including admin integration, serialization, and everything else. 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.
