#31938: Add a mechanism for page cache invalidation. -------------------------------------+------------------------------------- Reporter: Laurent Tramoy | Owner: nobody Type: New feature | Status: closed Component: Core (Cache system) | Version: 3.1 Severity: Normal | Resolution: duplicate 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 Carlton Gibson):
* status: new => closed * resolution: => duplicate * component: Utilities => Core (Cache system) * stage: Unreviewed => Accepted Comment: Hi Laurent. Thanks for the report. I was going to Accept this as a new feature — I've spent a good amount of time rifling through cache keys to work out which one to delete by hand. I think this would be a good addition. **But** it looks to me like #5815 is the same issue, so let's close as a duplicate. Can I ask you take your idea to the DevelopersMailingList and ask for some input of your thoughts for an implementation? I would be good if you want to take this on to push it forwards! 👍 -- Ticket URL: <https://code.djangoproject.com/ticket/31938#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 django-updates+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/064.27ed2f5862bfe1e4df45ba7f6ea7dc9d%40djangoproject.com.