#10790: Too many joins in a comparison for NULL.
-------------------------------------+-------------------------------------
Reporter: mtredinnick | Owner: akaariai
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by akaariai):
* owner: mtredinnick => akaariai
Comment:
I have update the work, it can be found from:
https://github.com/akaariai/django/compare/ticket_18748...ticket_18748_comb
Note that the work is now based on patch found from #18748 - the reason is
that I am very likely going to commit that patch soon, and because that
patch and this one conflict I didn't want to resolve conflicts again after
commit of #18748.
There is at least on thing I have to do: refactor the added patch for this
ticket. It has way too much stuff in one test method. Otherwise I don't
know of any issues in the patch and djangobench doesn't complain about
performance.
So, I will likely try to get this patch into Django soon enough.
--
Ticket URL: <https://code.djangoproject.com/ticket/10790#comment:42>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
