I would like for __exact=None to evaluate to "is null" and not "=null"
but after reading the developer mailing list on the question it seems
like they are set on the current behavior. So is there another way to
do it in a similarly simple way?
What I have now is something like:
f = SomeClass.objects;
if a == None:
f = f.filter(a__isnull=True)
else:
f.filter(a=a)
if b == None:
f = f.filter(b__isnull=True)
else:
f.filter(b=b)
if c == None:
f = f.filter(c__isnull=True)
else:
f.filter(c=c)
I was expecting to just be able to do:
f = SomeClass.objects.filter(a=a, b=b, c=c)
Is there some way to do this with the current code base?
Anders Hovmöller
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
