On Thu, Apr 2, 2009 at 9:29 PM, Dave Fowler <davefow...@gmail.com> wrote:
> > I'm about to do my umpteenth Django app and I'm just wondering if > there is a new standard (better) way to extend the User model. I've > used this method > > http://www.b-list.org/weblog/2006/jun/06/django-tips-extending-user-model/ > > And a few others, but all of them keep the User and Profile objects > separate which consistently adds a lot of extra code for me. The > largest issue is a command like this > > User.objects.all().select_related() > > Results in an N+1 query when you need the profile information. You > could base everything off of your profile > > Profile.objects.all().select_related() > > But it seems weird to base everything around the object that isn't > used for authentication. Is that what most people do? > > Thanks > > > Yes, the OneToOneField is still the prefered way to extend the user model, the issue with select related is the subjct of ticket #7270. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
