Changes between Version 1 and Version 2 of MultipleColumnPrimaryKeys


Ignore:
Timestamp:
01/27/2007 08:54:40 PM (9 years ago)
Author:
notnotpeter <petertripp@…>
Comment:

Formating

Legend:

Unmodified
Added
Removed
Modified
  • MultipleColumnPrimaryKeys

    v1 v2  
    44
    55= Current Status =
     6
    67[http://code.djangoproject.com/ticket/373 Ticket 373: Add support for multiple-column primary keys]
    78Progress is stalled as there has been insufficient design discussion as to how this might be implemented.
    89
    9 = Major Issues
     10= Major Issues =
     11
    1012Taken from [http://code.djangoproject.com/ticket/373#comment:3 Jacob's comment on Ticket 373]
    1113There are three basic problems in dealing with composite primary keys in Django.
     
    1618
    1719= Proposed Solutions =
     20
    1821Proposed solutions for the admin URL issue:
    1922"/app_label/module/pk1,pk2/" -- does not support text primary keys which include a comma.
     
    2124
    2225= Alternative methods =
     26
    2327Currently, you can "fake" it by declaring one of the keys to be primary in Django and adding a unique constraint to the model. (needs more info...examples?)
    2428
    2529= Links / Notes=
     30
    2631[http://code.djangoproject.com/ticket/373]
    2732Rails/ActiveRecord doesn't support this natively, but [http://compositekeys.rubyforge.org/] is an add-on which does
Back to Top