#23661: Site cache doesn't cache in a per-database basis
-------------------------------+--------------------
Reporter: Kronuz | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.6
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
The cache for `Site` (`SITE_CACHE`) should cache site objects for the
database the object comes from. If there is a router in place and the
current site is retrieved from one database, a second call for getting the
current site from a different database will return the wrong object for
that database.
Instead of using `SITE_CACHE` the way it's currently done, I propose using
the same caching scheme as the one used in `ContentType`'s `_cache`.
--
Ticket URL: <https://code.djangoproject.com/ticket/23661>
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/049.ffc00d5919b34d880a7ebc5c1cb1258e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
