Hi Ned, On Fri, 2006-06-09 at 10:07 -0400, Ned Batchelder wrote: > I am still using 0.91, and have a question about this Model > Inheritance issue in the current trunk. We use model inheritance in > our code, but in a specialized way: only the derived classes are used > concretely. The base classes are all abstract: there are no rows in > their tables, no objects are ever instantiated, and no queries are > made for the base classes. We do this to build common sets of fields > that are available on a number of different objects, which can then be > used polymorphically with Python duck-typing. > > Is this style of model inheritance still possible on the current > trunk?
No. You end up with the wrong manager for the child, from what I remember of this. You get the manager for the oldest ancestor class (the base of you hierarchy), so selecting "everything" will not give you what you want, for example. But I may be misremembering, so you should probably test this. There is certainly some hurdles with just this pure "field sharing" inheritance at the moment. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
