#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 ramiro):
Replying to [comment:10 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
I wouldn't add documentation that talks about multithreading misleading
people to think it's a supported configuration. If (as you know very
well) Django documentation makes no explicit mention about multithreading
being supported at all; the why should a warning about failures (with a
hypothetical multithreaded scenario reproduced not with threads but
concurrent processes) with a DB backend to a software (SQLite) that is the
one that supports concurrency to the lesser extent be added?
--
Ticket URL: <http://code.djangoproject.com/ticket/9409#comment:11>
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
-~----------~----~----~----~------~----~------~--~---
