#16484: Duplicate entry sessions error
----------------------------------+-------------------------------------
Reporter: hash.3g@… | Owner: nobody
Type: Bug | Status: closed
Component: contrib.sessions | Version: 1.3
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+-------------------------------------
Changes (by aaugustin):
* status: reopened => closed
* resolution: => duplicate
Comment:
This is suspiciously similar to #18557.
The conclusion [https://groups.google.com/d/topic/django-developers
/wvpysb-fXtc/discussion on the mailing list] was to use the READ COMMITTED
isolation level (recommended), or database-level autocommit of every query
(not recommended).
MySQL defaults to REPEATABLE READ, which appears to make such situations
intractable.
--
Ticket URL: <https://code.djangoproject.com/ticket/16484#comment:8>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
