Issue #6743
Updated by dalley over 4 years ago
By modifying a prior migration, we accidentally created a mismatch between the schema we expect and the schema Django seems to interpret and enforce, interpret, presumably due to some kind of optimization being employed. optimizations that Django employs. It seems that because Django sees that migration 0005 made the 'last_sync_revision_number' column nullable (it didn't, it was modified afterwards) [0], it ignores when migration 0009 tells Django to perform that migration later. Thus the 'last_sync_revision_number' column remains non-nullable. This impacts Pulp users by throwing the following error when creating new RPM repositories. ~~~ django.db.utils.IntegrityError: null value in column "last_sync_revision_number" violates not-null constraint ~~~ [0] https://github.com/pulp/pulp_rpm/pull/1694/files#diff-8882c765a6805ada6c8a8bafe3e3e5b8
.