#10868: _destroy_test_db exposes the production database to possibly destructive
actions from the unit tests
-------------------------------------+-------------------------------------
Reporter: ovidiu | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version:
Severity: Release blocker | Resolution:
Keywords: django.test | Triage Stage: Design
Has patch: 1 | decision needed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by julien):
Ok, considering those limitations with PostgreSQL, I would say the best
way is probably to temporarily swap the main thread's
`DBWrapper.settings_dict` attribute with a thread-local copy, then modify
that copy to point to the production database, then drop the test
database, and finally re-swap it with the original `settings_dict` value
for good measure, as I guess you had already suggested in comment:3.
--
Ticket URL: <https://code.djangoproject.com/ticket/10868#comment:15>
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 this group at
http://groups.google.com/group/django-updates?hl=en.
