Opened 12 months ago
Closed 12 months ago
#34561 closed Bug (invalid)
"DatabaseError: Forced update did not affect any rows" on SessionStore save()
| Reported by: | Daniel Nunes | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.sessions | Version: | 3.2 |
| Severity: | Normal | Keywords: | session, session error, session save |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
After a user login while working with mozilla-django-oidc, I came across this "DatabaseError: Forced update did not affect any rows" error on request.session.save().
This looks to me like a race condition where the session doesn't exist but we still try to update it.
Change History (2)
comment:1 by , 12 months ago
| Keywords: | session session error session save added |
|---|
comment:2 by , 12 months ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
As far as I'm aware, this should be handled by
mozilla-django-oidcnot silently ignored by Django. Please report it on their bugtracker.