#19031: Using @override_settings doesn't override DATABASES in threads +SQLite
-----------------------------------+--------------------------------------
Reporter: jonash | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | Version: 1.4
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Changes (by akaariai):
* status: new => closed
* needs_docs: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
I don't think we should claim that you can switch the used database in-
flight and expect everything to work. My guess is that the problem here is
no syncdb ran for the DB. You could try if things work if you run syncdb
manually in setUp().
Wontfixing this, as ensuring that the database is set up correctly, and is
also torn down correctly seems hard to do.
--
Ticket URL: <https://code.djangoproject.com/ticket/19031#comment:1>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
