id summary reporter owner description type status component version severity resolution keywords cc stage has_patch needs_docs needs_tests needs_better_patch easy ui_ux 15327 TEST_USER setting has become mandatory on Oracle Marco De Paoli nobody "upgrade from django 1.2.1 to django 1.2.5 I run tests and I obtained[[BR]] {{{ KeyError: 'TEST_USER' }}} My box is: * CentOS 5.4 * oracle-instantclient-basic-10.2.0.4-1.i386.zip * oracle-instantclient-devel-10.2.0.4-1.i386.zip * cx_Oracle 5.0.4 * Django 1.2.5 You can easily reproduce the problem: {{{ django-admin.py startproject testdjango cd testdjango python manage.py startapp testapp # edit settings to configure connection to db python manage.py test # KeyError: 'TEST_USER' }}} according to http://code.djangoproject.com/wiki/OracleTestSetup and http://docs.djangoproject.com/en/1.2/ref/settings/#test-user The TEST_USER setting is optional: ''The username of such user isn't the same as the 'USER' var, is derived from it by adding a 'test_' prefix. It '''can''' be overridden with the value of the 'TEST_USER' var.'' Since 1.2.1 this behavior has changed and now the setting is mandatory[[BR]] Working settings for django 1.2.5 are: {{{ DATABASES = { 'default': { 'ENGINE': 'django.db.backends.oracle', 'NAME': 'test', 'USER': 'dslcm', 'PASSWORD': '****', 'TEST_USER': 'test_dslcm', 'HOST': '', 'PORT': '', }, } }}} I wasn't able to find this information in release notes nor in documentation[[BR]] My humble :) advice is to restore the optionality of this setting, or, otherwise, upgrade the documentation" closed Database layer (models, ORM) 1.2 fixed TEST_USER Oracle blocker regression depaolim@… Accepted 0 0 0 0 0 0