On Wed, 2006-07-12 at 17:13 +0300, Jyrki Pulliainen wrote: > On 7/12/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: [...] > > When a test targets is executed, django-admin: > > 1) creates a test database named 'test_' + settings.DATABASE_NAME > > This is created to the database server being used? Have you thought of > spawning a new sqlite database to the memory and using that. That way > you could be sure that no extra data is left behind (when you > terminate the application, the sqlite goes down too). This would also > enable testing in enviroinments where there is only one postgres db > available for some reason.
If one wants to run the tests against in-memory SQLite, then you can use a settings file with the appropriate settings (there is nothing that says tests and "main" need to use the same settings file, in fact multiple settings files are easy and to be encouraged). However, any framework have to be able to test against all possible database configurations because of the need to test things like referential integrity, trigger behaviour, stored procedure actions, portable SQL, etc. 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 -~----------~----~----~----~------~----~------~--~---
