From fda55c71a8846364b9dc4f4efac4d7034ef6dd6f Mon Sep 17 00:00:00 2001 From: Marti Raudsepp Date: Sat, 5 Nov 2016 10:16:23 +0200 Subject: Fixed #27858 -- Prevented read-only management commands from creating the django_migrations table. MigrationRecorder now assumes that if the django_migrations table doesn't exist, then no migrations are applied. Reverted documentation change from refs #23808. --- tests/admin_scripts/tests.py | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) (limited to 'tests/admin_scripts') diff --git a/tests/admin_scripts/tests.py b/tests/admin_scripts/tests.py index 9ef2da83a0..e2d2a3bca1 100644 --- a/tests/admin_scripts/tests.py +++ b/tests/admin_scripts/tests.py @@ -22,7 +22,6 @@ from django.core.management import ( BaseCommand, CommandError, call_command, color, ) from django.db import ConnectionHandler -from django.db.migrations.exceptions import MigrationSchemaMissing from django.db.migrations.recorder import MigrationRecorder from django.test import ( LiveServerTestCase, SimpleTestCase, TestCase, override_settings, @@ -1339,15 +1338,12 @@ class ManageRunserver(AdminScriptTestCase): def test_readonly_database(self): """ - Ensure runserver.check_migrations doesn't choke when a database is read-only - (with possibly no django_migrations table). + runserver.check_migrations() doesn't choke when a database is read-only. """ - with mock.patch.object( - MigrationRecorder, 'ensure_schema', - side_effect=MigrationSchemaMissing()): + with mock.patch.object(MigrationRecorder, 'has_table', return_value=False): self.cmd.check_migrations() - # Check a warning is emitted - self.assertIn("Not checking migrations", self.output.getvalue()) + # You have # ... + self.assertIn('unapplied migration(s)', self.output.getvalue()) class ManageRunserverMigrationWarning(TestCase): -- cgit v1.3