Browse files

Fixed #3137 -- Added 'Clearing the session table' section to docs/ses…


git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent f21cbb4 commit fcdbb929183eacc18cfe9ab8af498aa120fc24b0 @adrianholovaty adrianholovaty committed Dec 30, 2006
Showing with 17 additions and 0 deletions.
  1. +17 −0 docs/sessions.txt
@@ -217,6 +217,23 @@ browser-length cookies -- cookies that expire as soon as the user closes his or
her browser. Use this if you want people to have to log in every time they open
a browser.
+Clearing the session table
+Note that session data can accumulate in the ``django_session`` database table
+and Django does *not* provide automatic purging. Therefore, it's your job to
+purge expired sessions on a regular basis.
+To understand this problem, consider what happens when a user uses a session.
+When a user logs in, Django adds a row to the ``django_session`` database
+table. Django updates this row each time the session data changes. If the user
+logs out manually, Django deletes the row. But if the user does *not* log out,
+the row never gets deleted.
+Django provides a sample clean-up script in ``django/bin/``.
+That script deletes any session in the session table whose ``expire_date`` is
+in the past -- but your application may have different requirements.

0 comments on commit fcdbb92

Please sign in to comment.