On Aug 26, 2008, at 2:13 PM, Malcolm Tredinnick wrote: > On Tue, 2008-08-26 at 10:57 -0700, diggs wrote: >> I'm just starting to port my app over to use nfa and the first thing >> that I'm seeing is that derived models are showing up twice in the >> admin. In my case I have a base VideoStory class and >> TwoPersonVideoStory class that derives from VideoStory using multi- >> table inheritance. When I create a new TwoPersonVideoStory it shows >> up >> under the list of VideoStorys as well. Is there a way to prevent >> this? > > No. The row in the VideoStory table has no way of knowing it's > linked to > a row in the TwoPersonVideoStory table at the database level and > Django > doesn't do a query over every possible descendent table every time it > queries the root table (you may think that sounds acceptable for one > table, but now add a few more subclasses and give them a few > subclasses > of their own and it rapidly becomes horribly inefficient without > trying > very hard).
Would it work if a ModelAdmin defined its own queryset() method that applied some base filters to remove rows it didn't want to show up in the ChangeList? --- David Zhou [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
