#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
----------------------------------+-------------------------------------
Comment (by anonymous):
Replying to [comment:9 jokerejoker]:
> This is still a problem for Django 1.5.1
There was no claim above that this would be "fixed" by Django 1.5.1, since
it's suspected the underlying problem is MySQL's default "reapeatable
read" transaction isolation level. There is no way (aside from including a
commit within `get_and_create` itself, which is completely unacceptable)
to "fix" this inside of Django. The fix is to change your transaction
isolation level to "read committed".
--
Ticket URL: <https://code.djangoproject.com/ticket/16484#comment:10>
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/075.ed77e40606bee6a37563c2807f0141e9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
