Fixed #5544 -- Fixed another typo in documentation, introduced as a result of the changes in [6333] and [6365]. Thanks for the report, xiaolianyi@gmail.com.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@6384 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Russell Keith-Magee 2007-09-20 02:02:21 +00:00
parent 4704412bb3
commit 6306400102
1 changed files with 1 additions and 1 deletions

View File

@ -205,7 +205,7 @@ An API is available to manipulate session data outside of a view::
datetime.datetime(2005, 8, 20, 13, 35, 0) datetime.datetime(2005, 8, 20, 13, 35, 0)
>>> s.save() >>> s.save()
If you're using the ``django.contrib.sessions.engine.db`` backend, each If you're using the ``django.contrib.sessions.backends.db`` backend, each
session is just a normal Django model. The ``Session`` model is defined in session is just a normal Django model. The ``Session`` model is defined in
``django/contrib/sessions/models.py``. Because it's a normal model, you can ``django/contrib/sessions/models.py``. Because it's a normal model, you can
access sessions using the normal Django database API:: access sessions using the normal Django database API::