#26797: Reverse `related_name` of a proxy not accessible to inherited proxies in
queryset
-------------------------------------+-------------------------------------
Reporter: mlorant | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: related_name | Triage Stage:
reverse relation | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by charettes):
* status: new => closed
* resolution: => duplicate
Comment:
Hi Maxime,
Thanks for your report.
As you've noticed this is a duplicate of #18012 which won't be backported
to 1.9 as it's not related to a security issue, a regression from 1.7, or
a bug in a new feature introduced in 1.8. You can have a look at our
[https://docs.djangoproject.com/en/1.9/internals/release-process
/#backwards-compatibility-policy backward compatibility policy] for more
details.
The release note was added under the ''Backwards incompatible changes in
1.10'' instead of the ''What’s new in Django 1.10'' where new feature are
documented which makes it clear to me it's not a new feature but if you
think the phrasing is inadequate please reopen with a suggested
alternative.
--
Ticket URL: <https://code.djangoproject.com/ticket/26797#comment:3>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.abc47aed7bc4155e707b3b0072e4047d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
