Well, it depends on what you want to do exactly, you could create something
like this:
class UserProfile(models.Model):
common_data....
class ClientProfile(UserProfile):
specific_data....
class StudentProfile(UserProfile):
specific_data....
class TeacherProfile(UserProfile):
specific_data....
...
AUTH_PROFILE_MODULE = 'appname.UserProfile'
This would ensure that 3rd party apps that don't know about your
3-user-types system work in your site, but whether you do this, or ignore
AUTH_PROFILE_MODULE, you'll have to set up a specific way of creating the
profiles on user creation. Save signals are your friend here, probably,
and/or the views you use to create the different types of user.
--
"The whole of Japan is pure invention. There is no such country, there are
no such people" --Oscar Wilde
|_|0|_|
|_|_|0|
|0|0|0|
(\__/)
(='.'=)This is Bunny. Copy and paste bunny
(")_(") to help him gain world domination.
--
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
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
