title: Django (nose) test speeding up with reuse_db not working
body: <p>I am using django-nose to run my unit tests in django (1.4).</p>
  
  <pre><code>TEST_RUNNER = 'django_nose.NoseTestSuiteRunner'
  </code></pre>
  
  <p>Creating the database takes a long time.</p>
  
  <p>So I found out putting this in settings.py:</p>
  
  <pre><code>os.environ['REUSE_DB'] = "1"
  </code></pre>
  
  <p>should do the trick.</p>
  
  <p>actually django itsellve gives this suggestion:</p>
  
  <pre><code>To reuse old database "&lt;path not very interesting&gt;/var/sqlite/unittest.db" for speed, set env var REUSE_DB=1.
  </code></pre>
  
  <p>of course you need to run it once (or after every database change) with this flag =0</p>
  
  <p>However, when you set the flag to 0, my tests end with the remark:</p>
  
  <pre><code>Destroying test database for alias 'default'...
  </code></pre>
  
  <p>So when I want to run it with reuse.... there is nothing to reuse... and I will get errors saying the table does not exist</p>
  
  <pre><code>DatabaseError: no such table: &lt;and than a table name&gt;
  </code></pre>
  
  <p>The test runs perfectly when set the reuse_db to 0</p>
  
  <p>I am using the test database alias in my development settings:</p>
  
  <pre><code>DATABASES = {
      'default': {
          'NAME': os.path.join(BUILDOUT_DIR, 'var', 'sqlite', 'development.db'),
          'TEST_NAME': os.path.join(BUILDOUT_DIR, 'var', 'sqlite', 'unittest.db'),
          'ENGINE': 'django.db.backends.sqlite3', 
          'USER': '',
          'PASSWORD': '',
          'HOST': '', 
          'PORT': '', 
          }
      }
  </code></pre>
  
  <p>I am not using the in-memory sqllite database for testing because I read somewhere this doesn't work well with django-nose.</p>
  
  <p>So how can I reuse the DB when it is destroying the databse in the end...</p>
  
  <p>according to this <a href="https://docs.djangoproject.com/en/1.4/topics/testing/#the-test-database" rel="nofollow">https://docs.djangoproject.com/en/1.4/topics/testing/#the-test-database</a> django is doing this, but it does not show how to prevent this (if I can), or how to use the reuse_db option.
  should I use other settings?</p>