"James Bennett" <[EMAIL PROTECTED]> writes: > On Jan 19, 2008 10:24 PM, Jim Crossley <[EMAIL PROTECTED]> wrote: >> Yes, I knew I could override the NAME, but I'd like to override the >> ENGINE,USER,PASSWORD,HOST, and PORT, too. Our settings are configured >> for mysql/innodb, to match our production environment. But as our >> test suite and initial_data grows, it takes a frustratingly long time >> to run the tests. I'd like to use the faster sqlite, but just for the >> tests. Can you suggest an approach? > > Yes. Create another settings file, and in it put the following: > > from your_real_settings import * > > DATABASE_ENGINE = 'sqlite3' > DATABASE_HOST = '/some/filename/'
So then I assume I must do something like this to run my tests? DJANGO_SETTINGS_MODULE=test.settings ./manage.py test Do you prefer that to having some kind of global variable indicating tests are being run that the normal settings file could query to know which db settings to use? It seems the TEST_DATABASE_NAME goes partially in that direction -- why not go all the way? :-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
