#35230: Cache ForeignObjectRel.get_accessor_name()
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: nobody
Type: | Status: assigned
Cleanup/optimization |
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* stage: Unreviewed => Accepted
Comment:
This is worth doing but if anyone runs into issues with this change future
when running data migrations the root cause is likely tickets such as
#27737 until #29898 is completed. It is well known that operating from
rendered models can cause all of sorts of issues with regard to caching of
relationship attributes, it should be a reason to avoid using rendered
models though and not to avoid caching relationship attributes.
It will be interesting to see if this has a noticeable effect on
[https://django.github.io/django-asv/ the benchmarks].
--
Ticket URL: <https://code.djangoproject.com/ticket/35230#comment:1>
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/0107018dbd6c2970-b16dcad8-31e1-4df6-89c7-ab41df486362-000000%40eu-central-1.amazonses.com.
