Thanks Rob,
I'm using the same approach here, but I don't really like to access some of
my fields in the template doing `user.get_profile.field` I would simply love
to do `user.field`. Also Sometimes I'm pointing to my profile instead of
User, to access the extra information so queries become more
Probably most of us are using the separate profile model, as
recommended.
I actually have multiple models associated with users on one project:
User (from auth)
UserInfo (things rarely accessed such as address, emergency contact
info, etc.)
UserProfile (my application specific profile)
I'm going
¿no one knows anything about this?
Thanks, regards
Miguel Araujo
2010/10/22 Miguel Araujo
> Hello everyone,
>
> I'm not very aware about what's the direction Django is taking about the
> User model and making it swappable. Meanwhile I would like to ask if
> inheriting the User class is advisabl
3 matches
Mail list logo
