#32424: in-memory test database does not work with multiprocessing.apply_async
-------------------------------------+-------------------------------------
Reporter: Tata Krushna | Owner:
Chaitanya | Arkaprabha Chakraborty
Type: Uncategorized | Status: closed
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: sqlite3, threading, | Triage Stage:
tests | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: assigned => closed
* resolution: => wontfix
Comment:
I fear like this won't be possible to do per the in-memory nature of such
databases.
It's one thing to serialize queries between multiple threads in a single
process but it's another one to coordinate it across multiple processes
that need to share the same memory.
Closing as ''wontfix'' as nothing seems to indicate this is even possible
and Django's core doesn't have any use for it.
--
Ticket URL: <https://code.djangoproject.com/ticket/32424#comment:3>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.dfc027437d06d2e9de58abcac68fa095%40djangoproject.com.
