#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):
I've attached a patch as a way of illustrating our recent discussions. A
few comments and questions about this patch:
* I'm not sure if it's worth eventually restoring the original settings
dict references. That'd be straight-forward in
`BaseDatabaseCreation.destroy_test_db()` but probably less so in
`DjangoTestSuiteRunner.teardown_databases()`.
* I'm not sure how/if this can be tested.
* How would be handle DBWrappers potentially being shared between threads?
--
Ticket URL: <https://code.djangoproject.com/ticket/10868#comment:18>
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.
