#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 famousactress@…):
I went through a similar exercise, attempted to move the logic into
trim_joins and ran into lots of the same problems... trimmed joins
sometimes need to 'come back' later on. I really like where this patch is
going, but of course it's unfortunate that it's scope will disqualify it
for Django 1.4. I'll try to put together a targeted unit test that proves
the regression I found and maybe we'll find a simpler fix for the
regression. Meanwhile, I've sent over a pull request with my unit test
cleanup from the original patches. Hopefully it's useful:
https://github.com/akaariai/django/pull/1
--
Ticket URL: <https://code.djangoproject.com/ticket/10790#comment:38>
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.
