#9409: "OperationalError: database is locked" with Python 2.6 multiprocessing
and
SQLite backend
------------------------------------+---------------------------------------
Reporter: mrts | Owner: nobody
Status: reopened | Milestone:
Component: Documentation | Version: 1.0
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by mrts):
Where do you get the impression I'm not aware that processes are used
instead of threads in `multiprocessing`? Concurrent processing idioms and
problems are the same whether `threading` or `multiprocessing` is used,
only GIL reduces concurrency (and hides some problems) in `threading`
context a bit. And I'm obviously launching that many processes to assure
that the problem indeed manifests, this is a test case.
The mailing list threads are relevant for having a general idea of the
issues. I hope the explanation that I've attached is sufficient, if you
find it is not or that I've missed something or made a mistake in the
explanation, please correct it and attach a new patch.
--
Ticket URL: <http://code.djangoproject.com/ticket/9409#comment:10>
Django <http://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
-~----------~----~----~----~------~----~------~--~---
