I've noticed a couple posts on this subject, but I don't understand what's going on. Can someone please explain.
The docs say "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." I'm using the following: django.contrib.auth.views.login django.contrib.auth.views.logout When I login through that first view, the session is created in the DB. When I logout with that other view, the record is still in the DB. Why? If I now log in as another user, the session that wasn't delete is used as this new user's session. Does this have something to do with support AJAX requests? Or is it too prevent memory leakiness through stale sessions lingering around? Or, have I misconfigured something? Please explain Now, of course, the user may never actually call that logout view, so it might stay in the DB anyway. But, certainly if another user comes along and logs into my app from the same computer, it shouldn't be remembering the session. I don't even want the same user to be remembering the session they had last time they logged in. I don't mind running a session clearly script each day. Do I have a subclass login and put a session.delete or something in there before each login? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
