Hi Martin!
On Wed, 09 Mar 2011 15:58:54 +0100, Martin Tiršel <[email protected]> wrote: > NO = False > YES = True > YES_NO_CHOICES = ( > (NO, 'no'), > (YES, 'yes') > ) > > to > > > NO = 0 > YES = 1 > YES_NO_CHOICES = ( > (NO, 'no'), > (YES, 'yes') > ) > > Then I get 0 or 1 for filter instead of True or False and it works. I > think that the admin takes the True/False parameter in URL as string and > does't convert it to bool. Aha! That's very interesting. I'm not sure whether this is really a bug or not--SQL is a bit strange about Boolean values sometimes--, but it looks like one, too. Would you like to open a ticket for this, referring to the URL of this thread in google groups? Please also state your database engine. I'd appreciate if you set Cc to my email address. ;-) Kind regards Michael -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
