So far it allows declaration and creation of primary key models. You
declare them in class Meta: primary_key = ('field', 'field', 'field').There is no ForeignKey/Relational? handlers as of right now, but the admin is mostly working. Alex Gaynor pointed out there is one unrelated change I accidently committed. The list_select_related changes I proposed. There is also an issue with URL resolving in the admin (its a 1.1 proposal) so it's using a , vs a / for the delimiter, but it's a simply setting change. On Nov 16, 5:50 pm, David Cramer <[EMAIL PROTECTED]> wrote: > http://github.com/dcramer/django-compositepks/tree/master# > > On Nov 16, 5:25 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> > wrote: > > > On Sun, Nov 16, 2008 at 5:19 PM, David Cramer <[EMAIL PROTECTED]> wrote: > > > Also keep in mind that work has been done, but as I haven't had a lot of > > > spare time to continue it (attempt #3?). It's a very complex problem as > > > well, like Jacob mentioned. You have to deal w/ the legacy use of single > > > primary keys, as well as the new composites. While I almost have a fully > > > functioning version (barring ForeignKey support) it's still going to take > > > a > > > little bit. > > > If you'll share your code — #373 is begging for a patch... — others > > can use it as a starting place. > > > Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
