News for hackers. Stuff that matters.

A comment on Django 1.10 released. Parent comment

Re:Django 1.10 released by rtpg on Monday August 01, 2016 @10:09PM (#12207433)
Ah, I feel bad, because I ran into this twice and didn't report this properly. The situations I ran into happened whenever I would combine filters and excludes, along with some joins. The system would simply drop filters, and just do a plain SELECT on the table. But ever since the 1.8 ORM update, I have no longer been able to reproduce this, so have assumed it was fixed through cleaning up the internals.

I did report a related bug[0] where the ORM gets confused by complex queries, but it didn't just drop the filter. It blew up, which is better but still a bit concerning.

[0]: https://code.djangoproject.com/ticket/24386

[ Parent | on HN ]
Re:Django 1.10 released by jsmeaton on Monday August 01, 2016 @10:26PM (#12207487)
Exclude filters are awful and very unintuitive if you know SQL in my experience. I'd much prefer to use negated filters like: `.filter(id__notequal=3)`. I'm giving a talk at djangocon AU in a couple of weeks where I'll step through examples like this.
[ Parent | on HN ]
Re:Django 1.10 released by rtpg on Monday August 01, 2016 @10:48PM (#12207557)
Right. Worse case, you can use `~Q` or the like. The way I recall it, this didn't solve the issue (as in: something more fundamental than "using exclude instead of filter"), but I no longer have the example...
[ Parent | on HN ]