Author: Alex
Date: 2009-11-23 10:43:25 -0600 (Mon, 23 Nov 2009)
New Revision: 11767
Modified:
django/branches/soc2009/multidb/docs/topics/http/sessions.txt
Log:
[soc2009/multidb] Added extra docs on configuring the database-backed session
store. Patch from Russell Keith-Magee.
Modified: django/branches/soc2009/multidb/docs/topics/http/sessions.txt
===================================================================
--- django/branches/soc2009/multidb/docs/topics/http/sessions.txt
2009-11-23 16:43:17 UTC (rev 11766)
+++ django/branches/soc2009/multidb/docs/topics/http/sessions.txt
2009-11-23 16:43:25 UTC (rev 11767)
@@ -24,14 +24,6 @@
The default ``settings.py`` created by ``django-admin.py startproject``
has
``SessionMiddleware`` activated.
- * Add ``'django.contrib.sessions'`` to your ``INSTALLED_APPS`` setting,
- and run ``manage.py syncdb`` to install the single database table
- that stores session data.
-
-.. versionchanged:: 1.0
- This step is optional if you're not using the database session backend;
- see `configuring the session engine`_.
-
If you don't want to use sessions, you might as well remove the
``SessionMiddleware`` line from ``MIDDLEWARE_CLASSES`` and
``'django.contrib.sessions'``
from your ``INSTALLED_APPS``. It'll save you a small bit of overhead.
@@ -46,6 +38,22 @@
some setups it's faster to store session data elsewhere, so Django can be
configured to store session data on your filesystem or in your cache.
+Using database-backed sessions
+------------------------------
+
+If you want to use a database-backed session, you need to add
+``'django.contrib.sessions'`` to your ``INSTALLED_APPS`` setting.
+
+If you want to store your session data on a database other than ``default``
+alias, you should set the :setting:`SESSION_DB_ALIAS` setting.
+
+Once you have configured your installation, run ``manage.py syncdb``
+to install the single database table that stores session data.
+
+.. versionadded:: 1.2
+ The :setting:`SESSION_DB_ALIAS` setting was added in Django 1.2. It
+ is not required in earlier versions.
+
Using cached sessions
---------------------
@@ -86,6 +94,9 @@
enough, but if you need that last bit of performance, and are willing to let
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`_.
+
Using file-based sessions
-------------------------
@@ -97,6 +108,7 @@
where Django stores session files. Be sure to check that your Web server has
permissions to read and write to this location.
+
Using sessions in views
=======================
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=.
