That's a very good question, Dougal, and I'm too much of a noob to be
able to answer it. I THINK those lookups are lazy, but I'd love to
hear from someone who knows more about it.
On Feb 14, 8:47 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> The problem I have with this is that, if I'm co
The problem I have with this is that, if I'm correctly understand what
goes on, when I do a select_related all the related objects are
retrieved. In this case, if a user has made, say, 4000 posts plus
other types of contributions, it seems like it's pulling in a lot of
unnecessary data.
Am I misu
I just use a generic list view and send it
user_dict = {
'queryset': GpUser.objects.all(),
}
GpUser is my model that extends auth.user
On Feb 14, 2:47 am, "Aidas Bendoraitis" <[EMAIL PROTECTED]>
wrote:
> Your profile perhaps is related by a foreign key to the user, which
> means that theore
Your profile perhaps is related by a foreign key to the user, which
means that theoretically one user can have several profiles.
Therefore, in my opinion, you should get the profiles and use
select_related() for related users.
profiles =
UserProfile.objects.select_related().order_by('user__id')[
Hi,
I have a site with users and an additional user_profile to store extra
information like a signature, avatar, etc.
I cannot figure out how to use a single query to get a list of users
and at the same time join in their user_profile information.
Currently I have this:
users = User.objects.al
5 matches
Mail list logo
