#16715: Wrong JOIN with nested null-able foreign keys
-------------------------------------+-------------------------------------
Reporter: sebastian | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: SVN
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: join, values, | Needs documentation: 0
nested, foreign key, null-able | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
Yeah, debugging leftover. Should always do a git grep pdb before posting a
patch :)
As for stabilizing, yeah, that is a problem. The recursive comment refers
to my original idea of doing
{{{
self.promote_joins(child_join_aliases)
}}}
for every alias that got promoted. However, it seemed that this is not
necessary. But now that you mention it, it would still be the correct
thing to do. The fix is easy to make, except I am not totally sure how to
get the child joins of an alias... I will check how to do that.
--
Ticket URL: <https://code.djangoproject.com/ticket/16715#comment:13>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
