diff options
| author | Tommy Beadle <tbeadle@arbor.net> | 2015-04-14 10:43:57 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-08-24 08:59:20 -0400 |
| commit | d3fdaf907db6a5be4d0391532d7e65688c19e851 (patch) | |
| tree | f29086e0f08340e6eed939c8f55ac97475f4aac1 /AUTHORS | |
| parent | 45ed19de687d324d3ba852eea93b1afa575e482f (diff) | |
Fixed #23727 -- Inhibited the post_migrate signal when using serialized_rollback.
When using a TransactionTestCase with serialized_rollback=True,
after creating the database and running its migrations (along with
emitting the post_migrate signal), the contents of the database
are serialized to _test_serialized_contents.
After the first test case, _fixture_teardown() would flush the
tables but then the post_migrate signal would be emitted and new
rows (with new PKs) would be created in the django_content_type
table. Then in any subsequent test cases in a suite,
_fixture_setup() attempts to deserialize the content of
_test_serialized_contents, but these rows are identical to the
rows already in the database except for their PKs. This causes an
IntegrityError due to the unique constraint in the
django_content_type table.
This change made it so that in the above scenario the post_migrate
signal is not emitted after flushing the tables, since it will be
repopulated during fixture_setup().
Diffstat (limited to 'AUTHORS')
| -rw-r--r-- | AUTHORS | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -698,6 +698,7 @@ answer newbie questions, and generally made Django that much better: Tome Cvitan <tome@cvitan.com> Tomek Paczkowski <tomek@hauru.eu> Tom Insam + Tommy Beadle <tbeadle@gmail.com> Tom Tobin torne-django@wolfpuppy.org.uk Travis Cline <travis.cline@gmail.com> |