On Fri, 2006-06-30 at 13:59 +0000, [EMAIL PROTECTED] wrote: > > I understand what you are wanting to do. I'm wondering why you can't > > create the dictionary inside runtests.py and then poke it inside > > settings.DATABASE? > > That's a good idea, I hadn't thought of that. Are there any objections > to reserving the keys 'django_test_db_a' and 'django_test_db_b' in > settings.DATABASE for use in multiple db tests? If that's ok, where > would I document that they are reserved?
There's a constant at the top of runtests.py called TEST_DATABASE_NAME at the moment. If you put your constant(s) (tuple?) around there with a similar name, it will be easy enough to find. The current testing framework detects if a database with TEST_DATABASE_NAME already exists and asks for permission to stomp on it; you should do the same. Try running the tests with a django_test database already created and you'll see what I mean. So it's not vital that everybody knows about these database names, since we do not destroy data without permission. But if you put them in constants at the top of the file, finding them all will be easy. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers -~----------~----~----~----~------~----~------~--~---
