59👍
request.session
is a SessionStore object with a unique session_key.
The session_key is created as soon as the attribute is accessed. But the session object itself is only saved to the database after the view has been processed (in the process_response method of the session middleware) by calling the save method of the SessionStore object.
It’s not really documented, but looking at the source code I guess you are supposed to create a new session object like this:
if not request.session.exists(request.session.session_key):
request.session.create()
You could also create custom session middleware, that makes sure your new session object is always available before any of your views tries to access it:
from django.conf import settings
from django.contrib.sessions.middleware import SessionMiddleware
class CustomSessionMiddleware(SessionMiddleware):
def process_request(self, request):
engine = import_module(settings.SESSION_ENGINE)
session_key = request.COOKIES.get(settings.SESSION_COOKIE_NAME, None)
request.session = engine.SessionStore(session_key)
if not request.session.exists(request.session.session_key):
request.session.create()
(Of course you must reference your new session middleware via the SESSION_ENGINE inside your settings.py
)
But be aware – this approach will generate a new session object for every request if the user’s browser does not support cookies …
1👍
if you want to destroy session i would suggest a better idea is first use django shell.
from django.contrib.sessions.models import Session
Session.objects.all() #you see all sessions
Session.objects.all().delete()
in last query you can filter according to your need. and hit a query
- [Django]-Laravel's dd() equivalent in django
- [Django]-What is a django.utils.functional.__proxy__ object and what it helps with?
- [Django]-How to render HTML in string with Javascript?