I went with something along those lines so what I do now in my view
is (pseudo-code of course):
queryset = my_filter(SomeClass, a=a, b=b, c=c)
It's very strange to me that I need to do this, because I would
expect the creation and fetching to be symmetrical. The behavior of
"a=a" is radically different in the constructor of a model and then
during fetching. This only seems logical if you are very used to SQL.
Leaky abstractions are bad, aren't they? ^_-
On Mar 5, 2007, at 00:31 , oggie rob wrote:
>
>> 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?
>
> I'm not sure of the exact syntax, but you can use a dictionary to
> achieve this fairly easily. Something like
> args = {}
> if a == None:
> args['a__isnull'] = True
> else:
> args['a'__exact] = a
> ...
> SomeClass.objects.filter(**args)
>
> -rob
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
