On 5/10/07, Diego <[EMAIL PROTECTED]> wrote: > > In my model I have an abstract class ServAbstract and ahother subclass > ServA and ServB derived from ServAbstract. > In the databse It might generate three tables: > > table_ServAbstract > table_ServA > table_ServB > > , and when by the admin interface I add a new ServA, > table_ServAbstract y table_ServA might be modified. > > By the moment I use onoToOne relation betwen table_ServAbstract and > table_ServA , and betwen table_ServAbstract and table_ServB, but I > thing is not the right way. > > Any ideas?
At present, a OneToOne relation is your only real option. We have plans to introduce model inheritance - including abstract base classes - in the near future. See http://code.djangoproject.com/wiki/ModelInheritance for details. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
