mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-04 02:48:35 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Fixed #19031 -- Added a warning when using override_settings with 'DATABASES'

Browse source
This commit is contained in:
Joeri Bekker 2013-05-18 13:43:51 +02:00 • committed by Tim Graham
parent b82a2c4138
commit 66f3d57b79
6 changed files with 64 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

17
docs/topics/testing/overview.txt
View file

@ -1403,6 +1403,23 @@ The decorator can also be applied to test case classes::
the original ``LoginTestCase`` is still equally affected by the
decorator.
.. warning::
The settings file contains some settings that are only consulted during
initialization of Django internals. If you change them with
``override_settings``, the setting is changed if you access it via the
``django.conf.settings`` module, however, Django's internals access it
differently. Effectively, using ``override_settings`` with these settings
is probably not going to do what you expect it to do.
We do not recommend using ``override_settings`` with :setting:`DATABASES`.
Using ``override_settings`` with :setting:`CACHES` is possible, but a bit
tricky if you are using internals that make using of caching, like
:mod:`django.contrib.sessions`. For example, you will have to reinitialize
the session backend in a test that uses cached sessions and overrides
:setting:`CACHES`.
You can also simulate the absence of a setting by deleting it after settings
have been overriden, like this::