#29062: "database table locked errors" when using sqlite in-memory database with
LiveServerTestCase
-------------------------------------+-------------------------------------
Reporter: Juozas Masiulis | Owner:
| Christophe Baldy
Type: Bug | Status: closed
Component: Testing framework | Version: 2.0
Severity: Normal | Resolution: fixed
Keywords: sqlite, testing, | Triage Stage: Ready for
databases | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"855f5a36e7c8e7a8ce3f62d6ef8c9ae3e073ae3d" 855f5a36]:
{{{
#!CommitTicketReference repository=""
revision="855f5a36e7c8e7a8ce3f62d6ef8c9ae3e073ae3d"
Fixed #29062 -- Prevented possibility of database lock when using
LiveServerTestCase with in-memory SQLite database.
Thanks Chris Jerdonek for the implementation idea.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29062#comment:24>
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/01070184a90e66bc-f5a9b556-c455-4f11-a76d-93a876d0f037-000000%40eu-central-1.amazonses.com.
