On 03/29/2011 02:46 PM, Shawn Milochik wrote: > I'm not proposing a change to Django itself or suggesting that this > should be a standard practice. I do think that this is a fairly clean > solution for an individual to use to solve this problem if they have > it. > > They can create a custom manager on the abstract class that would > return an iterable, perhaps using itertools.chain() of the querysets.
Ah, I didn't realize that's the direction you were headed. Yeah, you can do this, and I've done it; it starts to hurt as soon as you want, say, sorting + pagination without pulling all of both tables into memory. > 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. Yup. Carl -- 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.
