REUSE_DB=1 support for multiple databases

[gabewb]

(cross-posted here: http://stackoverflow.com/questions/17279806/is-there-a-way-to-tell-django-nose-to-handle-multiple-databases)

In settings.py I have:

DATABASES = {
    'default': {
        'ENGINE': 'mysql_pymysql',
        'NAME': 'OST_DEV_1',
        'USER': 'root',
        'PASSWORD': '',
        'HOST': 'localhost',
        'PORT': '3306',
    },
    'umc': {
        'ENGINE': 'mysql_pymysql',
        'NAME': 'UMC',
        'USER': 'root',
        'PASSWORD': '',
        'HOST': 'localhost',
        'PORT': '3306',
    }
}

This works fine (but slowly, of course):

./manage.py test myapp

But this fails:

REUSE_DB=1 ./manage.py test myapp
DatabaseError: (1146, u"Table 'OST_DEV_1.tblMfg' doesn't exist")

But tblMfg is in UMC, not OST_DEV_1.

We currently use 'using' manually for the objects that are in UMC:

        active_mfgs = Mfg.objects.using('umc').filter(status="ACTIVE")

Is there a way to tell django-nose to treat these two databases separately?

[enoren]

I am seeing this issue as well with Django 1.5 when I was not seeing the issue with Django 1.4. It appears that from 1.4 to 1.5 Django would establish a connection to the databases ahead of calling the setup_databases method of the NoseTestSuiteRunner which would have the effect that the test for _should_create_database would come back with information about the main database and not the test database since the preexisting connection was created against the main DB.

The fix for this is easy and is really just adding a call to connection.close() right before doing the _should_create_database call in NoseTestSuiteRunner.setup_databases()

I will submit a patch for this.