#32980: Improve performance of related manager attribute access
-------------------------------------+-------------------------------------
Reporter: Keryn Knight | Owner: Keryn
Type: | Knight
Cleanup/optimization | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Keryn Knight):
* needs_better_patch: 1 => 0
Comment:
Marking as ready to have eyes on it once again, naturally can revert back
to needs improvement.
A question I've raised on the ticket, which I reproduce for historical
purposes here, is:
> There's one thing that isn't handled, because I'm not sure if/how it can
actually happen, and that's the case of a ManyToManyField which is
symmetrical and the branch entered is self.reverse is True. As far as I
know, it's impossible to get a reverse manager for symmetrical m2ms, but
if it's possible, it would currently pose a problem because get_cache_name
defers to get_accessor_name and that returns None for symmetries, so there
would be the possibility of a collision.
--
Ticket URL: <https://code.djangoproject.com/ticket/32980#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.aaa0881af6a27b61dd2efc0f842984ab%40djangoproject.com.
