#23011: Getting user ID from a request shouldn't hit the database
---------------------------------+------------------------------------
Reporter: BertrandBordage | Owner: nobody
Type: New feature | Status: closed
Component: contrib.auth | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by BertrandBordage):
OK. I find it sad to have an extra SQL request on every view with a
logged user, but since we can’t fetch all the sessions of a user to
invalidate them on delete or password change, I guess there is no other
option…
--
Ticket URL: <https://code.djangoproject.com/ticket/23011#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.2c9a73104876298885d6fb1eaa5b61b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
