Changes between Version 1 and Version 2 of Ticket #27054, comment 6
- Timestamp:
- Aug 12, 2016, 7:52:51 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #27054, comment 6
v1 v2 1 For each connection: `loader.check_consistent_history` calls `recorder.MigrationRecorder.applied_migrations` to get the set of migrations that have already been applied to the database on the other end of the connection. `MigrationRecorder.applied_migrations` calls `MigrationRecorder.ensure_schema` so that it can query the table underlying `MigrationRecorder.Migration`. It is `MigrationRecorder.ensure_schema` that catches ` django.db.utils.ProgrammingError` and raises `MigrationSchemaMissing` in its place.1 For each connection: `loader.check_consistent_history` calls `recorder.MigrationRecorder.applied_migrations` to get the set of migrations that have already been applied to the database on the other end of the connection. `MigrationRecorder.applied_migrations` calls `MigrationRecorder.ensure_schema` so that it can query the table underlying `MigrationRecorder.Migration`. It is `MigrationRecorder.ensure_schema` that catches `DatabaseError` and raises `MigrationSchemaMissing` in its place. 2 2 3 3 Conceptually `MigrationRecorder.applied_migrations` is a read-only operation with respect to the database, but nevertheless it does attempt write operations as an implementation side-effect.