#25690: Migration operations should be ordered to prevent all columns from being
removed
----------------------------+--------------------------------------
Reporter: mcrowson | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: mysql | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Comment (by hackedd):
This does indeed happen on MySQL when removing the last column from a
table. The problem can be worked around by changing the order of
operations in the migration.
Maybe it would be a good idea to drop and recreate the table if all
columns are dropped?
--
Ticket URL: <https://code.djangoproject.com/ticket/25690#comment:2>
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/066.e261161d7295e27a33f5b9c61126b64e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
