On Wed, May 28, 2014, Leonardo Giordani <giordani.leona...@gmail.com> wrote:
>I usually solve such issues with Inheritance. I feel comfortable with it >because it lets me (in your example) to manage both ResearchStudent and >ResearchStaff independently, while keeping the Researcher parent model >available to deal with "global" queries and data interaction. It it were a case where abstract inheritance would work, I would agree. Unfortunately, the Researcher model can't be abstract (because it has its own relations with Publications). If I use multi-table inheritance, that solves part of the problem. However I don't know how well it would work if I have a Researcher, who at some point needs to be a ResearchStudent and maybe later becomes ResearchStaff. Regards, Daniele -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/20140528123744.1377784185%40smtpauth.cf.ac.uk. For more options, visit https://groups.google.com/d/optout.
