#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 still a little more checking. And now I wonder about the whole
trim_joins concept: Why do we first add a join to a parent table, but then
immediately proceed to trim that join? Wouldn't it make a lot more sense
to not produce the parent join at all... This would mean that the join
trimming logic would need to go into setup_joins.
Of course, doing the above "little" change isn't this ticket's problem :)
--
Ticket URL: <https://code.djangoproject.com/ticket/10790#comment:28>
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.
