The multi-table inheritance stuff in queryset-refactor does essentially what is mentioned in that article, except it merges the namespace so that it's easier to use. That being said, it seems that OneToOneField has been improved as well, for those who want to be explicit about that link.
On Apr 25, 1:26 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On Fri, Apr 25, 2008 at 10:23 AM, AmanKow <[EMAIL PROTECTED]> wrote: > > Could you elaborate or point to elaboration on why non-abstract > > inheritance is a bad fit for extending user? > > http://www.b-list.org/weblog/2007/feb/20/about-model-subclassing/ > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
