Re: Desired behaviour when passing a non boolean to filter(*__isnull)

Monday, September 30, 2019 at 5:47:12 PM UTC+3, André Ericson wrote: >> >> Hello, >> >> I came across the discovery (due to a bug on our code) that it's possible >> to pass a non-boolean to the __isnull filter. What would be the desired >> behavior here? &

Re: Desired behaviour when passing a non boolean to filter(*__isnull)

Super. I'll look into it! On Monday, September 30, 2019 at 5:32:44 PM UTC+2, Adam Johnson wrote: > > Hi André > > I think Django should use the truthy value. Please open a ticket with your > bug report and then a PR. > > Thanks, > > Adam > > On Mon, 30 Sep

Desired behaviour when passing a non boolean to filter(*__isnull)

Hello, I came across the discovery (due to a bug on our code) that it's possible to pass a non-boolean to the __isnull filter. What would be the desired behavior here? Should we raise an exception or should Django use the truthy value? If the second case is the desired behavior I have found a b

Tests failing on postgres 9.6

Hi, I'm having troubles with a couple of tests on postgres 9.6. I've created a ticket here: https://code.djangoproject.com/ticket/28234 Because Jenkins is still on 9.5 I would appreciate if someone could try to reproduce it on their setup with 9.6. Thanks. André Ericson -- Yo