#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):
I don't know how to proceed, it seems most of the core developers are
really busy, especially those who know the ORM. One way is to go to
#django-dev and try to get somebody interested. Finding somebody to review
this would be the first step.
I definitely do think we should keep this ticket restricted in scope. When
this gets committed, then maybe move forward. I do think the ORM needs
some restructuring in the future. But that is not this ticket's problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/16715#comment:18>
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.
