On Jul 21, 2:39 am, "Gwyn Evans" <[EMAIL PROTECTED]> wrote: > Just wondered if I'm missing something, or if it's just not been an > issue to anyone... > > Looking at the DB testing docs, it seems that it tries to use a > 'TEST_<dbname>', for testing. This is a bit of a problem with Oracle, > where a new DB is a rather 'heavyweight' thing and may not be possible > if using something like Oracle XE. The equivalent functionality with > Oracle is handled by changing schemaes (sp?) which would typically be > done by supplying a different username (& password) within the same > DB, but there didn't seem to be any way of tweaking the testing > framework to do this? > > /Gwyn
The Oracle backend uses a custom module to create and destroy the test "database", and it actually just creates a new schema and tablespace, not a full database (take a look at django/db/backends/oracle/ creation.py for the full details). Hope that answers your question, Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
