27.12.2012 13:08, Shai Berger kirjoitti:
Hi all,I'm seeing a problem with testing on Oracle, in a setting where there are two defined databases that reference the same connection parameters (this is done to enable operations in two parallel, separate transactions); the 'other' database is not treated as a test database. This means that, during tests, operations on it are performed on the 'production' database (this is all in a development environment, thankfully). Has anyone else run into this? Django==1.4.3 Thanks, Shai.
I assume that you're referring to test setup instructions on https://code.djangoproject.com/wiki/OracleTestSetup page?
You should see that there is defined TEST_USER, TEST_TBLSPACE and TEST_TBLSPACE_TMP variables to different names since those are ones used when running tests.
Django uses main user just to connect database and to create test users. Main user needs enough permissions (I've usually set that to DBA to make life easier) to enable creation of test user and needed tablespaces.
You can though have two different users there and even two different database instances if you do have those. Then there is no need to provide those custom values.
-- Jani Tiainen - Well planned is half done and a half done has been sufficient before... -- 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?hl=en.
