Changes between Version 6 and Version 7 of CompositePrimaryKeyDesignNotes

Timestamp:

Jul 22, 2010, 8:02:52 AM (14 years ago)

Author:

hartror

Comment:

--

CompositePrimaryKeyDesignNotes

@@ -3 +3 @@
 Collating design considerations, options and decisions here to help get this feature moving.
 
+== Design Questions ==
+How do you define multiple primary keys? The "neatest" solution would be to allow primary_key=True on multiple fields but this may be precluded by other design considerations.
+
+How do you foreign key onto a table with a composite foreign key?
+
 == Affected Areas ==
 
 === Models ===
+Need a way of defining the primary key.
+
+Generation of the create table SQL.
+
+A solution for foreign keying onto a table with a composite primary key.
 
 === Queries ===
+Model.objects.get(pk=foo) needs to be supported, probably using a tuple or dictionary though there is mention of the comment framework overlapping with this.
+
+=== Forms ===
 
 === Admin ===
+Expect there is a large amount of work in here making sure all the model inspection and form generation works.
+
+The other thing mentioned has been the url to object mapping which should be able to be handled with some nice url escaping.
 
 === Serialization ===
-
-=== Forms ===
+Code needs to be looked at further but all the foreign keying is likely to need attention.
 
 == Relevant Discussions ==