#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 been having second thoughts about this. It feels plain wrong that any
connection to the production database is ever made during any stage of the
tests' execution. I haven't got the chance to investigate this yet, but
I'd like to find a way to connect to the database server without actually
selecting any database at all, and then run the "`DROP DATABASE`"
statement on the test database. The same goes for the initial creation of
the test database as well.
--
Ticket URL: <https://code.djangoproject.com/ticket/10868#comment:13>
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.
