Changes between Version 1 and Version 2 of Ticket #36652, comment 4
- Timestamp:
- Oct 10, 2025, 3:45:24 PM (4 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #36652, comment 4
v1 v2 1 I should also mention that if the old migrations are removed, so that only the squashed migrations exist, then it doesn't matter if the migration names are a set or list. The issue where this is a problem seems to only be at the point where both old migrations and the squashed migrations exist. Basically when you are about to deploy the squashed migrations for the first time and deploy it to a site, so it adds them into the d b_migrations table.1 I should also mention that if the old migrations are removed, so that only the squashed migrations exist, then it doesn't matter if the migration names are a set or list. The issue where this is a problem seems to only be at the point where both old migrations and the squashed migrations exist. Basically when you are about to deploy the squashed migrations for the first time and deploy it to a site, so it adds them into the django_migrations table.