On Mon, 2008-10-20 at 01:29 +0300, Erik Allik wrote:
> CollegeTeam.objects.filter(team=game.team1) |
> CollegeTeam.objects.filter(team=game.team2)
That's certainly possible, but it's marginally more heavyweight than
doing it at the filter level (but only a tiny bit).
> But I would instead recommend:
> CollegeTeam.objects.filter(team__in=[game.team1, game.team2])
Alternatively:
from django.db.models import Q
CollegeTeam.objects.filter(Q(team=team1) | Q(team=team2))
Q-objects are documented in the database API. They exist primarily so
that you can "and" and "or" things together like this.
Most database optimisers will end up producing exactly the same query at
the lowest level when using either Erik's approach or mine. Erik's form
is probably slightly clearer in this case (where everything is of the
same type). On the other hand, the Q() approach is the only way when you
are creating disjunctions from things of different types (e.g. team name
is "team1" or home ground is "shizzle park").
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
