#29062: Sqlite in memory database does not work for testing.
-------------------------------------+-------------------------------------
Reporter: Juozas | Owner: nobody
Masiulis |
Type: Bug | Status: new
Component: Testing | Version: 2.0
framework | Keywords: sqlite, testing,
Severity: Normal | databases
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I am getting database table locked errors, when running tests which use
sqlite in memory database.
This issue was introduced with this commit:
https://github.com/django/django/commit/bece837829eafbc22f2598dadf82c9a8364b085a
I know this because reversing this commit resolves the issue for me.
If sqlite in memory testing is no longer supported, it should be mentioned
in the documentation. If it is supported, there needs to be some parameter
in the settings to use liveserver without multithreading. Or just make a
new class liveservermultithreaded.
--
Ticket URL: <https://code.djangoproject.com/ticket/29062>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.560350e70e0509776987ee9b14203a24%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
