Ah! You're correct. I get it now. Thanks!
--~--~-~--~~~---~--~~
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,
You're dancing all around it. I'm pretty sure its:
poll__id__exact=1 (two underscores both times)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
>
> Then you probably want it to read:
> choices.get_values(fields=['poll', 'votes'], poll_id__exact=1)
>
> i.e. your "field" is "poll_id" and the lookuptype is "exact"
> which translates to "poll_id__exact", and THEN the equals sign
> and what value you are asking it to match.
>
> --
> Glenn
On Fri, Mar 17, 2006 at 10:57:14PM -0800, [EMAIL PROTECTED] wrote:
> No, one underscore doesn't work:
> choices.get_values(fields=['poll', 'votes'], poll_id=1)
> returns
> TypeError: got unexpected keyword argument 'poll_id'
>
> I'm using two underscores because that's my (limited)
No, one underscore doesn't work:
choices.get_values(fields=['poll', 'votes'], poll_id=1)
returns
TypeError: got unexpected keyword argument 'poll_id'
I'm using two underscores because that's my (limited) understanding of
the field__lookuptype syntax of the API documentation
5 matches
Mail list logo