#16043: Specialization cache should be filled/shared with parent object cache
(multitable inheritance)
-------------------------------------+-------------------------------------
Reporter: Piotr Czachur | Owner: Paulo
Type: | Status: assigned
Cleanup/optimization |
Component: Database layer | Version: master
(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
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"bfb746f983aa741afa3709794e70f1e0ab6040b5" bfb746f9]:
{{{
#!CommitTicketReference repository=""
revision="bfb746f983aa741afa3709794e70f1e0ab6040b5"
Refs #16043 -- Refactored internal fields value cache.
* Removed all hardcoded logic for _{fieldname}_cache.
* Added an internal API for interacting with the field values cache.
Thanks carljm and MarkusH for support.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16043#comment:10>
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/064.cc319cb66c47c2751539792e1f9ca786%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
