#25530: Deferred foreign keys operations fail when the column is changed during
the
same migration
------------------------------+------------------------------------
Reporter: simonphilips | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by simonphilips):
I don't think squashmigrations really is to blame here. The migration
process itself gets stuck over valid input that could have been written
manually as the order of these operations makes perfect sense from a
coder's point of view. What is the reason for delaying these SQL
statements until after all operations have run? Why are they not run right
after each operation?
--
Ticket URL: <https://code.djangoproject.com/ticket/25530#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.b70ffa4f2b474c0b55a712c1add8adc3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
