#11987: destroy_test_db can destroy the production database in some situations
----------------------------------------+-----------------------------------
Reporter: eronen | Owner: nobody
Status: closed | Milestone:
Component: Testing framework | Version: 1.1
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm unclear of the sequence of events that can cause this to be a problem.
If you hit Ctrl C, the python process is killed. Unless I'm missing
something, the value stored in settings.DATABASE_NAME at that point is
irrelevant - it won't be shared with anything, or used by anything that
could destroy data.
I'm also unclear which code you are updating. If you want to submit a
patch, use diff.
--
Ticket URL: <http://code.djangoproject.com/ticket/11987#comment:1>
Django <http://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.
