omat skrev: > Thanks for the pointer, Nis. > > Model inheritance made my models so much DRYer that it will be hard to > give up, at least psychologically... > > And, except for the managers, it worked just as I would expect, and > for the managers, it was easy to patch. >
Just to make sure I understand, your expected behavior is - Each model gets a db table which include fields from its ancestors - Managers and (other) methods are inherited as if they were defined on the subclass - There is no common interface for subclasses of a model class. Correct? I would perhaps call this "class templating" rather than "subclassing", but I can definitely see its usefulness. Note that you get the probably undesired sideeffect of defining the Ortho class as a model - which may cause some confusion if people use syncdb and friends, and probably in other cases as well. Yours Nis Jorgensen --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
