summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/releases/1.7.txt7
-rw-r--r--docs/topics/http/sessions.txt5
2 files changed, 12 insertions, 0 deletions
diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt
index 10826829a8..aa68b722b6 100644
--- a/docs/releases/1.7.txt
+++ b/docs/releases/1.7.txt
@@ -154,6 +154,13 @@ Minor features
follow the :setting:`SESSION_COOKIE_SECURE` and
:setting:`SESSION_COOKIE_HTTPONLY` settings.
+:mod:`django.contrib.sessions`
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+* The ``"django.contrib.sessions.backends.cached_db"`` session backend now
+ respects :setting:`SESSION_CACHE_ALIAS`. In previous versions, it always used
+ the `default` cache.
+
:mod:`django.contrib.sitemaps`
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
diff --git a/docs/topics/http/sessions.txt b/docs/topics/http/sessions.txt
index 8bef7f2ee5..fb66034e7b 100644
--- a/docs/topics/http/sessions.txt
+++ b/docs/topics/http/sessions.txt
@@ -93,6 +93,11 @@ session data be expunged from time to time, the ``cache`` backend is for you.
If you use the ``cached_db`` session backend, you also need to follow the
configuration instructions for the `using database-backed sessions`_.
+.. versionchanged:: 1.7
+
+Before version 1.7, the ``cached_db`` backend always used the ``default`` cache
+rather than the :setting:`SESSION_CACHE_ALIAS`.
+
Using file-based sessions
-------------------------