Database Flushing in Django's TransactionTestCase

You've made an important observation about a potential discrepancy between the documentation and the actual implementation. Based on the provided context, there was indeed a change in how Django handles database flushing in TransactionTestCase.

According to the Django 1.5 release notes:

Previously, the test database was truncated before each test run in a TransactionTestCase. In order to be able to run unit tests in any order and to make sure they are always isolated from each other, TransactionTestCase will now reset the database after each test run instead.

This change was made to ensure test isolation and allow tests to run in any order. The current documentation appears to still reference the pre-1.5 behavior when it mentions flushing "at the start" of each test run.

Your observation about the code flushing the database at the end of the test run is correct based on the release notes. The documentation should be updated to reflect this behavior change to avoid confusion.

The correct behavior is that Django resets/flushes the database after each test in a TransactionTestCase, not before, which ensures that:

1. Each test starts with whatever state the database is in after initial setup
2. After the test completes, the database is reset to ensure the next test isn't affected

This would be a good candidate for a documentation update to ensure consistency between the implementation and documentation.