On Jun 29, 1:28 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > Actually it might be nice if the top parent class table had a > > content_type field (or similar to avoid coupling to > > contrib.contenttypes) so we could easily deduce the leaf class. > > ...The reason is that it > breaks inheriting from third-party classes
yes, that makes total sense > Or you can manually include a type_code attribute in your > parent model (since it's something you have created yourself). yes, I'll try this. I guess override save() and if the content_type isn't set then look it up and set it. that should only happen on create at which point the leaf class type is definitely known. > Relational > databases and object-oriented inheritance have some mismatches (search > for "Vietnam of computer science" brilliant :) let's not go to Iraq then. but you've done a great job here. with newforms-admin its all working without problems for me. yes, my Company class has 4 subclasses. when you click through to view a Contact (generic parent class) I'm at that point figuring out what the class is and simply relocating. also : you could always do a left join across all tables and then just check which ones' pointer fields came back not null. that sounds cheap. but the parent class doesn't really know all of its subclasses. you would have to do this query by supplying a list of leaf classes that it could then trace up the parents to the grandpappy and collect all of those tables. -cx > Regards, > Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
