mirror of
https://github.com/django/django.git
synced 2025-06-05 03:29:12 +00:00
[4.1.x] Fixed #32749 -- Doc'd PyMemcacheCache defaults.
Backport of bb2c5f69f47466fa52f3cf2727d10b3ebd79a4da from main
This commit is contained in:
parent
e40b77365f
commit
72358f0110
@ -149,6 +149,15 @@ on the IP addresses 172.19.26.240 (port 11211), 172.19.26.242 (port 11212), and
|
|||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
By default, the ``PyMemcacheCache`` backend sets the following options (you can
|
||||||
|
override them in your :setting:`OPTIONS <CACHES-OPTIONS>`)::
|
||||||
|
|
||||||
|
'OPTIONS': {
|
||||||
|
'allow_unicode_keys': True,
|
||||||
|
'default_noreply': False,
|
||||||
|
'serde': pymemcache.serde.pickle_serde,
|
||||||
|
}
|
||||||
|
|
||||||
A final point about Memcached is that memory-based caching has a
|
A final point about Memcached is that memory-based caching has a
|
||||||
disadvantage: because the cached data is stored in memory, the data will be
|
disadvantage: because the cached data is stored in memory, the data will be
|
||||||
lost if your server crashes. Clearly, memory isn't intended for permanent data
|
lost if your server crashes. Clearly, memory isn't intended for permanent data
|
||||||
|
Loading…
x
Reference in New Issue
Block a user