In my application I have students, professors and staff. Staff members do not need a profile but professors and students each need a different profile. I\'d rather not implement
Have you rad http://docs.djangoproject.com/en/dev/topics/auth/#auth-profiles?
That's the standard solution.
With Django 1.1, which is currently in beta, I would implement a proxy model.
class MyUser(User):
class Meta:
proxy = True
def get_profile(self):
if self.role == 'professor':
return ProfessorProfile._default_manager.get(user_id__exakt=self.id)
elif self.role == 'student':
return StudentProfile._default_manager.get(user_id__exakt=self.id)
else:
# staff
return None
get_profile needs the caching code from the original and so on. But essentially you could do something like that.
With Django 1.0.x you could implement derived classes based on User, but this might break code in other places. For stuff like that I love proxy classes, which just add python functionality without changing the database models.