On Feb 20, 6:07 am, Beres Botond <boton...@gmail.com> wrote:
> To be honest I don't really see why you would need multiple user
> profile models,
> instead of having one user profile model, and each entry would define
> a different
> user profile.

What do you mean by "one user profile model, and each entry would
define a different user profile"?

Do you mean to have my single user profile model have many foreign
keys hanging off of it pointing to other models?

Or do you mean have a single user profile model with lots of instance
data?

Imagine an app where you have users who are teachers, students, or
parents.  You track different information about teachers (which
courses they teach) vs. parents (relationship to student mom/dad,
etc).

I wouldn't want to cram all of that stuff into a single user profile
model and then have to figure out which sets of fields apply at
runtime.  If it's just instance data and isn't a foreign key to
another model, then it won't persist over time.

Right?


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to