On Mon, 2010-02-01 at 04:33 -0600, James Bennett wrote:
> On Mon, Feb 1, 2010 at 3:59 AM, Kenneth Gonsalves <law...@au-kbc.org> wrote:
> > Anyway, player.getcoursehandicap() works - but not within 'filter'
>
> Why would you expect it to? Python method definitions are not legal
> SQL, so you can't pass a Python method into a SQL query and expect it
> to work. If you want to further filter the results of a query using
> Python code, then do it in Python code.
It would've been nice to work, albeit in an inefficient way, such that
the code could be translated to something like ...
for player in self.all():
if player.getcoursehandicap in range(0..16):
yield player
Either way, I usually end-up adding such methods to the model's manager,
eg this (very inefficient method that can be optimized later) ...
class PlayerManager(models.Manager):
def filter_by_coursehandicap(self, range):
ids = [ player.id for player in self.all() \
if player.getcoursehandicap() in range ]
return self.filter(id__in=ids) # or something
class Player(models.Model):
# ....
objects = PlayerManager()
So, even if very inefficient, you can still chain conditions
together ...
Player.objects.filter_by_coursehandicap([0..16]).exclude(something=value).all()
--
Alexandru Nedelcu
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@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.
