#16715: Wrong JOIN with nested null-able foreign keys
-------------------------------------+-------------------------------------
Reporter: sebastian | Owner: nobody
Type: Bug | Status: new
Milestone: | 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: 1 | Has patch: 1
UI/UX: 0 | Needs tests: 1
| Easy pickings: 0
-------------------------------------+-------------------------------------
Changes (by carljm):
* version: 1.3 => SVN
* severity: Release blocker => Normal
Comment:
Thanks for the report and the patch! Sorry the patch hasn't been reviewed
yet; sometimes it takes a little while (especially with bugs like this one
that affect deep and sensitive ORM internals - tends to look like a time
sink to potential reviewers!). If you'd like to draw some attention to the
bug, a post to the django-developers mailing list about it (perhaps
demonstrating some cases where it causes real problems in your code) would
be a reasonable way to do that.
Nonetheless, I'm moving the severity back to Normal. We have fairly
concrete guidelines about what constitutes a release-blocking bug: if it's
a security problem or causes data-loss or a crash, or if its a regression
from a previous Django release. This bug should be fixed (thus its
Accepted), but it doesn't fall into any of the above categories, so it
won't block a release.
--
Ticket URL: <https://code.djangoproject.com/ticket/16715#comment:5>
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.
