Automattic / Automattic/wp-memcached

Future support of wp_cache_flush_group()

Open
#170 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
PHP
Stars
172
Forks
52
PR merge metrics
No merged PRs in 30d

Description

Hi,

It seems that the current version does not support flushing groups of keys (e. g. via _wp_cache_flush_group()_). Hower, this would be important, because some WP plugins delete transients by direct DB calls using wildcards.

Here is an example from Swift Performance:

`$wpdb->query("DELETE FROM {$wpdb->options} WHERE option_name LIKE '_transient_swift_performance_%'");
`

As the exact names of the keys are not known at the moment of deletion, it's impossible to flush these keys when they reside in memcached. To flush keys in memcached, the exact name of these keys needs to be know, right?

Are there any plans to support _wp_cache_flush_group()_ in the near future? Or any known workarounds for situation like this?

Thanks for your effort and all the work you've been doing so far!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the requested wp_cache_flush_group() behavior and the Swift Performance SQL example in the issue. Compare the exact-key limitation described for memcached with WordPress object-cache behavior, then determine whether a concrete implementation or documented workaround is possible. Done means an agreed scope and verified approach, but the issue does not name files or tests to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
memcached, php, wordpress
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.