#20418 closed Bug (fixed)
django.contrib.sessions not needed when using cookie-session-backend
Reported by: | Owned by: | Neven Munđar | |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Normal | Keywords: | session |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | yes |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
The documentation says nothing about that you don't need the app django.contrib.sessions when using cookie-session-backend. The docs says only that you need it in some cases, and that you can remove it if you don't need sessions at all.
Change History (8)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Needs documentation: | set |
---|---|
Triage Stage: | Unreviewed → Accepted |
comment:3 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:4 by , 11 years ago
Documentation update is available from this branch: https://github.com/nmundar/django/tree/ticket_20418
Cookies-based backend keeps all the data in the cookie so it does not need to access the database. Because of that there is no need for Session table in the db that gets created when django goes through INSTALLED_APPS settings.
comment:5 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Merged in [d9c01da1]
In the future, please following the commit message guidelines ("Fixed #XXXXXX -- Commit description") so that the ticket will automatically be closed when the pull request is merged.
https://docs.djangoproject.com/en/dev/internals/contributing/committing-code/#committing-guidelines
Related to #7836.