Changes between Version 9 and Version 10 of MultipleColumnPrimaryKeys


Ignore:
Timestamp:
Apr 2, 2009, 4:30:20 PM (15 years ago)
Author:
Tobu
Comment:

another status update and ml thread

Legend:

Unmodified
Added
Removed
Modified

  • MultipleColumnPrimaryKeys

    v9 v10  
    55= Current Status =
    66
     7Current state is that the issue is accepted/assigned and being worked on, and there is a partial implementation at http://github.com/dcramer/django-compositepks. The implementation allows having composite primary keys. However, support for composite keys is missing in {{{ForeignKey}}} and {{{RelatedManager}}}. As a consequence, it isn't possible to navigate relationships from models that have a composite primary key.
    78
    8 Current state is that the issue is accepted/assigned and being worked on, and there is a partial implementation at http://github.com/dcramer/django-compositepks (discussed at http://groups.google.com/group/django-developers/browse_thread/thread/4b2370a0652d9135 ). The implementation allows having composite primary keys. However, support for composite keys is missing in {{{ForeignKey}}} and {{{RelatedManager}}}. As a consequence, it isn't possible to navigate relationships from models that have a composite primary key.
     9Discussions:
     10* http://groups.google.com/group/django-developers/browse_thread/thread/eac7c296c3797f5a for David Cramer's initial patch
     11* http://groups.google.com/group/django-developers/browse_thread/thread/4b2370a0652d9135 for the composite foreign key API design
    912
    1013= Major Issues =
Back to Top