On Sun, Aug 23, 2009 at 1:54 PM, Andrea Zilio <m.ep...@gmail.com> wrote:
> > So seems that this idea was in fact rejected because of the O(# of > nodes in the inheritance tree) joins > needed to get all the fields from subclass tables. > You may want to loook at Alex's post on the subject: http://lazypython.blogspot.com/2009/02/second-look-at-inheritance-and.htmlfor a solution to apply on your own projects. Note that his code was written before Malcolm wrote proxy classes, Alex's code could now be improved to not query the subclasses but return proxy classes to them effectively avoiding the O(#..) queries untill you try to access subclass data ;) Regards, Marc --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
