#18726: Combination of F() expression with query seems to confuse sql compiler's
table aliases
-------------------------------------+-------------------------------------
Reporter: bugs@… | Owner: nobody
Type: Bug | Status: reopened
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
I rewrote the test case into expressions regress. I know at least of two
different bugs happening here:
1. The joins are "reverse trimmed" in a way that causes the query error
in split_exclude() -> set_start().
2. The F() expr is added to the query, then split_exclude() need is
seen, and the F() expr is again added to the subquery.
Even after bypassing the two above issues there is still something else
going on.
I am not sure if the test case is correct - at least it shows the U4
reference error, see
https://github.com/akaariai/django/compare/ticket_18726
--
Ticket URL: <https://code.djangoproject.com/ticket/18726#comment:6>
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.
