#10790: Too many joins in a comparison for NULL.
-------------------------------------+-------------------------------------
Reporter: mtredinnick | Owner:
Type: Bug | mtredinnick
Component: Database layer | Status: new
(models, ORM) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by akaariai):
I did some work on doing the removal beforehand. Some things broke, while
fixing them more things broke and so on...
I do agree fixing this is important, getting efficient SQL is important.
To me it seems one part of the problem is that once generated joins which
are then trimmed away can be later on reused. Causes all sorts of
problems. However, this is needed so that certain things work (run a
query, pickle it, unpickle it, rerun it -> same query string generated).
Complex stuff...
--
Ticket URL: <https://code.djangoproject.com/ticket/10790#comment:33>
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.
