#17998: database threading issue with dev server and sqlite
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by akaariai):
* cc: anssi.kaariainen@… (added)
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* needs_docs: => 0
Comment:
I have looked into this a little, but I can't see where the connection is
shared between the threads. Any ideas? It should be impossible to get the
same `DatabaseWrapper` in different threads unless explicitly shared. Of
course, it is possible there is a but making it not so impossible, which
would be more serious.
While I haven't reproduced this bug, I am still going to mark this
accepted, as I have seen some strange threading errors, too (caused by
using ipdb in my case, though).
--
Ticket URL: <https://code.djangoproject.com/ticket/17998#comment:1>
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 this group at
http://groups.google.com/group/django-updates?hl=en.
