On Tue, Mar 29, 2011 at 11:11 AM, Carl Meyer <c...@oddbird.net> wrote: > Hi Jordan, > > On 03/29/2011 11:40 AM, Jordan MacDonald wrote: >> I have three models, structured like so: >> >> Document >> -Presentation >> -Spreadsheet ...
>> I'd like to be able to write >> Document.objects.all(). I'd then like to be able to iterate over this >> enumerable and have each object cast to its proper class. ... > I'm not sure I'd want to have yet another variety of inheritance as a > first-class feature of the Django ORM; the array of existing options > with MTI, abstract inheritance, and proxy models is quite confusing > enough to new users! 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. -- 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.
