On Thu, 2009-03-05 at 12:54 -0800, madhav wrote: > I will be frequently running testcases for my django project. But one > fine day it occured to me that django actually checks the > settings.DATABASE_NAME db actual existence while running testcases.
It happens that the normal startup procedure for things uses the DATABASE_NAME setting. This is because we need a connection to the database server and for that requires a connection to an actual (existing) database that Django has permissions to connect to (so system databases might well be out of bounds). > Why is this so. All I thought was django will be taking the > settings.DATABASE_NAME and creates a test db called 'test_' + > settings.DATABASE_NAME. It also checks whether the database with the > name = settings.DATABASE_NAME, is actually existing or not(for > creating the test db)? Ideally speaking, only name should be checked > but not the actual existence of the db right? It's such a minor thing to create an empty database that matches the name in your settings file that it's not worth worrying about. Hopefully the above explanation clarifies why it's not simply an oversight. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
