Fixed #4914 -- Documented the Session.modified attribute for forcing session saves. Thanks, Thomas Güttler and SmileyChris.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@5869 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
6d31e431c3
commit
a564adb8e1
|
@ -190,6 +190,12 @@ deleted::
|
||||||
# request.session['foo'] instead of request.session.
|
# request.session['foo'] instead of request.session.
|
||||||
request.session['foo']['bar'] = 'baz'
|
request.session['foo']['bar'] = 'baz'
|
||||||
|
|
||||||
|
In the last case of the above example, we can tell the session object
|
||||||
|
explicitly that it has been modified by setting the ``modified`` attribute on
|
||||||
|
the session object::
|
||||||
|
|
||||||
|
request.session.modified = True
|
||||||
|
|
||||||
To change this default behavior, set the ``SESSION_SAVE_EVERY_REQUEST`` setting
|
To change this default behavior, set the ``SESSION_SAVE_EVERY_REQUEST`` setting
|
||||||
to ``True``. If ``SESSION_SAVE_EVERY_REQUEST`` is ``True``, Django will save
|
to ``True``. If ``SESSION_SAVE_EVERY_REQUEST`` is ``True``, Django will save
|
||||||
the session to the database on every single request.
|
the session to the database on every single request.
|
||||||
|
|
Loading…
Reference in New Issue