#30966: Migration crashes due to foreign key issue, depending on otherwise
irrelevant order on MySQL.
-------------------------------------+-------------------------------------
Reporter: Peter Thomassen | Owner: Hasan
| Ramezani
Type: Bug | Status: assigned
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: migration mySQL | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Hasan, the changes in `django/db/migrations/state.py` from comment:7 are
likely desired but the assertion in `Options` were more of a way to test
which operation currently break this contract. From your submitted PR only
three `migrations` tests were failing with these assertions including the
one you added even on SQLite.
Again, I suspect the cause is #27737 and the `TODO` in
`AlterField.state_forwards`. The fact the rendering is delayed prevents
`Token` from being refreshed adequately.
--
Ticket URL: <https://code.djangoproject.com/ticket/30966#comment:11>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/072.90cc0548f9d27b3f4f05aeffb6a90ea2%40djangoproject.com.
