#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):
Your last comment is misleading as a) Django is generally threadsafe and I
personally use it routinely with threaded apache and mod_wsgi with no ill
effects, b) this is not a thread, but a general concurrency issue that
pops up even in Google cache (see http://209.85.135.104/search?q=cache
:kEMOo-HuvzgJ:www.rkblog.rk.edu.pl/w/p/django-
nginx/+django+OperationalError:+database+is+locked ) for live sites
running on top of `mod_python`. You are perhaps right that "threaded
environment" and "thread" are not appropriate terms, a more generic term
that encompasses both processes and threads might be required. Someone
could amend the patch with such a term.
--
Ticket URL: <http://code.djangoproject.com/ticket/9409#comment:12>
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
-~----------~----~----~----~------~----~------~--~---
