#15894: SITE_CACHE does not invalidate in multiprocess environments
------------------------------------+------------------------------------
Reporter: Kronuz | Owner: nobody
Type: Bug | Status: new
Component: contrib.sites | Version: 1.3
Severity: Normal | Resolution:
Keywords: cache invalidation | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+------------------------------------
Comment (by virtosubogdan):
Replying to [comment:17 claudep]:
> #25783 was a duplicate with [https://github.com/django/django/pull/5692
a patch].
The proposed patch is on the right track, most of the people here agree
that the cache framework should be used for this.
However the global variable should not remain, clearing the cached values
for all the sites would not be possible anymore. Clearing the ones that
hit the current process would only add more inconsistencies. Also if the
current site is not retrieved with Site.object.get_current() before the
save operation, the pre/post hooks will not clear the cached data for that
site, leaving other processes to use obsolete data.
Should the proposed and closed patch be reviewed/updated or can a new
patch be submitted?
--
Ticket URL: <https://code.djangoproject.com/ticket/15894#comment:18>
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.d85f0249e5137ae3a1d583f769ab081a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
