Thanks for the pointer, Alex. Yes, I have seen that part of the documentation. Even using model inheritance, however, I still have to list at a minimum 8 * 12 = 96 different models (8 different versions of 12 different models). Then, I still must manually specify each related field, since Django doesn't know that two particular model subclasses are associated, and can't infer the correct relationship. There are in total 23 such fields, which means I now must list at least 96 models (each with a manually specified Meta class listing its db_table), and 8 * 23 = 184 different related fields.
So while it is possible to do this with model inheritence, at least the most obvious solution involves a lot of code duplication. Best, Trevor Caira On May 25, 1:12 pm, "Alex Ezell" <[EMAIL PROTECTED]> wrote: > On Sun, May 25, 2008 at 12:30 AM, Trevor Caira <[EMAIL PROTECTED]> wrote: > > How can I model this situation most simply, and with the least code > > duplication, in django? > > Hi Trevor, > Have you looked at the Model Inheritance part of the documentation? > > http://www.djangoproject.com/documentation/model-api/#model-inheritance > > You could abstract all the common elements into one model (the > abstract base class) and have the other models subclass that parent. > They would then contain only the parts of the model that differ from > model to model. > > /alex --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
