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 obscure and less elegant if I need to access User though my Profile `userprofile__user__username__exact`
If there is no better option, I will try to wrap everything in some helpers, Regards, Miguel Araujo 2010/10/25 Rob <[email protected]> > 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 to break UserProfile into EmployeeProfile and StudentProfile > at some point or keep UserProfile add the other two profile types. > Depends on how looking into Django model polymorphism goes :-) > > I prefer the separation of profile and login in my case. Many > students do not want or need logins to the system. > > > > > On Oct 24, 6:32 am, Miguel Araujo <[email protected]> wrote: > > ¿no one knows anything about this? > > > > Thanks, regards > > Miguel Araujo > > > > 2010/10/22 Miguel Araujo <[email protected]> > > > > > > > > > > > > > > > > > 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 advisable or not. As I have read many > places > > > obscure bugs can happen and my code will be in production. > > > > > I'm using now an AUTH_PROFILE_MODULE at the moment, but I don't realy > like > > > this approach, as it makes my class hierarchy more complicated. > > > > > Thanks, best regards > > > Miguel Araujo > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<django-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
