| 3 | | But now I'm still stuck trying to figure out what to do about it. Is there any kind of work around I could use? Is this something that I did wrong? Or is this a bug in Django? Any help would be appreciated. |
| | 3 | But now I'm still stuck trying to figure out what to do about it. Is there any kind of work around I could use? Is this something that I did wrong? Or is this a bug in Django? |
| | 4 | |
| | 5 | For now, I have placed a patch into "django/db/backends/base/creation.py" (inside of the create_test_db() function), in which I use "call_command()" twice (once with 'migrate', 'accounts', which causes an exception I catch and ignore, then once more with just 'migrate'). This allows me to run my unit tests. |
| | 6 | |
| | 7 | Obviously, this is terrible, since I don't want to have to patch Django with an ugly workaround every time I install it. There must be a better way, but what is it? |
| | 8 | |
| | 9 | Any help would be appreciated. |