#36652: Django Squashed Migrations Randmonly Passing/Failing Based On Set
Iteration
Order
--------------------------------+--------------------------------------
Reporter: Jayden Kneller | Owner: (none)
Type: Bug | Status: new
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Comment (by Jayden Kneller):
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
db_migrations table.
--
Ticket URL: <https://code.djangoproject.com/ticket/36652#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070199cfdde0af-5aaacf1e-8935-4a97-ae56-6ba8d93b7468-000000%40eu-central-1.amazonses.com.
