On 9/1/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
Thanks for the feedback.
These are reasonable concerns. I have just committed (r3706) a TEST_DATABASE_NAME setting; by default, this has a value of None, which will cause the test database to use the same 'test_' + DATABASE_NAME scheme; however, if you provide a value, that name will be used instead.
This setting is then used by runtests; settings.TEST_DATABASE_NAME is hardcoded to 'django_test_db', just as it was with the old runtests.
Yours,
Russ Magee
I can work around this, sure, but I'd propose to allow to
overwrite the default test database name for the test suite
somehow, preferably on the command line of runtests.py.
Thanks for the feedback.
These are reasonable concerns. I have just committed (r3706) a TEST_DATABASE_NAME setting; by default, this has a value of None, which will cause the test database to use the same 'test_' + DATABASE_NAME scheme; however, if you provide a value, that name will be used instead.
This setting is then used by runtests; settings.TEST_DATABASE_NAME is hardcoded to 'django_test_db', just as it was with the old runtests.
Yours,
Russ Magee
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-developers@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-developers
-~----------~----~----~----~------~----~------~--~---
