Cool. Well, maybe I can look into how abstract base classes are currently implemented and see if there's a way to generate query sets for all derived classes from the parent.
Thanks for the insight! On Mar 29, 12:40 pm, Carl Meyer <c...@oddbird.net> wrote: > On 03/29/2011 12:40 PM, Jeremy Dunck wrote: > > > What about keeping abstract inheritance in this case, but allowing > > Document.objects.* to work by returning instances of the subclasses. > > Filtering, etc. would only work based on the Document base class. > > > It would mean doing some unions, but would still fit the use case > > pretty well, I think. > > I'd certainly be intrigued to look at a patch that implemented that. > > 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.
