summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMike Lissner <mlissner@michaeljaylissner.com>2020-07-30 13:49:57 -0700
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2021-05-20 06:24:48 +0200
commit6e155d280dbe4bab171619654d8abc4b7f197e78 (patch)
tree8dd4825cb5f59e0f0a95356fec1939d85587c7a4 /docs
parent536c155e67fd82ef23975919bd55ccec966f96f8 (diff)
Added note about culling in database cache backend docs.
Co-authored-by: Mariusz Felisiak <felisiak.mariusz@gmail.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/cache.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt
index 7bf9fcbbde..6ae1e1e376 100644
--- a/docs/topics/cache.txt
+++ b/docs/topics/cache.txt
@@ -195,6 +195,10 @@ In this example, the cache table's name is ``my_cache_table``::
}
}
+Unlike other cache backends, the database cache does not support automatic
+culling of expired entries at the database level. Instead, expired cache
+entries are culled each time ``add()``, ``set()``, or ``touch()`` is called.
+
Creating the cache table
~~~~~~~~~~~~~~~~~~~~~~~~