diff options
| author | Julien Phalip <jphalip@gmail.com> | 2012-01-30 08:27:50 +0000 |
|---|---|---|
| committer | Julien Phalip <jphalip@gmail.com> | 2012-01-30 08:27:50 +0000 |
| commit | f1dc83cb9877d349df88674a0752ddf42657485b (patch) | |
| tree | 26733cc3aa3cc6cd0a9fc2e40c4d2c180570432b /docs | |
| parent | b5d0cc9091c04e7d6f0d7eed5b6d409805430ed6 (diff) | |
Fixed #10868 -- Stopped restoring database connections after the tests' execution in order to prevent the production database from being exposed to potential threads that would still be running. Also did a bit of PEP8-cleaning while I was in the area. Many thanks to ovidiu for the report and to Anssi Kääriäinen for thoroughly investigating this issue.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17411 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/1.4.txt | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/docs/releases/1.4.txt b/docs/releases/1.4.txt index c5128b10f2..8a7bfb2011 100644 --- a/docs/releases/1.4.txt +++ b/docs/releases/1.4.txt @@ -946,6 +946,19 @@ apply URL escaping again. This is wrong for URLs whose unquoted form contains a ``%xx`` sequence, but such URLs are very unlikely to happen in the wild, since they would confuse browsers too. +Database connections after running the test suite +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The default test runner now does not restore the database connections after the +tests' execution any more. This prevents the production database from being +exposed to potential threads that would still be running and attempting to +create new connections. + +If your code relied on connections to the production database being created +after the tests' execution, then you may restore the previous behavior by +subclassing ``DjangoTestRunner`` and overriding its ``teardown_databases()`` +method. + Features deprecated in 1.4 ========================== |