You haven't really provided a reason why to 'do it the django way', rather than inheriting from User.
You do make a valid point about the separate data being in a different table: the difference would be that with using UserProfile, you need to either do the .select_related() yourself, of have a second db query when you do a .get_profile(). With the inheritance method, django will do the joins for you. This may actually bite: there are some circumstances where a join is more expensive than a second query. In either case, right now is probably not the time to worry about it. Wait until it becomes a performance issue. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/aYGkovCMC_4J. 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.
