> The reason I thought this should go in the branch is that I'm not > completely satisfied with it, but also I'm kind of 'stuck' with some > bits of it (not really hard, just keep putting them off - there is some > duplicated code to do with OneToOne and ForeignKey, some 2.4 isms, and > that deleted object display stuff in the admin is kind of wierd ).
Ok, so I think I've fixed most of these except the deletion display in the admin. That one still just looks insane... Also method_delete works, but probably does way too much work to assure it doesn't cause any constraint violations... And OneToOne is still pretty strange in that it derives from an integer field which is clearly going to be wrong whenever you extend something that has a non integer pk ..(true in trunk as well). I still think it could do with branch bashing, but... http://code.djangoproject.com/ticket/1020
