If you need to be able to filter and search across models, you could try haystack.
http://docs.haystacksearch.org/dev/searchqueryset_api.html#filter I've setup a site with a real base class, done queries on that and then returned the child classes. It worked, but it felt pretty hacky all the way through. (You solution has a much nicer interface than mine, so your's wouldn't feel as bad I'm guessing.) If you go ahead and make the switch to haystack you'll be able to search across any and all of your models, without worrying about inheritance. I've been very happy with haystack since switching to it. Alex On Mar 29, 3:20 pm, Johannes Dollinger <emulb...@googlemail.com> wrote: > Am 29.03.2011 um 20:46 schrieb Shawn Milochik: > > > They can create a custom manager on the abstract class that would > > return an iterable, perhaps using itertools.chain() of the querysets. > > > It depends on what they expect to do with the output of this custom > > manager, and they'd obviously lose the ability to treat this output as > > a queryset by using additional sorts & filters and such. But if the > > goal is to be able to get instances from all subclasses at once then > > this is a viable solution, FWIW. > > FWIW, here is an implementation that does just > that:https://github.com/emulbreh/shrubbery/blob/master/shrubbery/db/union.py > > __ > Johannes -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
