#31186: Migration crash when changing CharField to TextField and removing
related
unique constraint on MySQL.
-------------------------------------+-------------------------------------
Reporter: Kailegh | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: wontfix
Keywords: migration, | Triage Stage:
TextField, CharField | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* cc: Markus Holtermann (added)
* status: new => closed
* version: 2.2 => master
* resolution: => wontfix
Comment:
Thanks for this report, however this is a MySQL caveat and I don't think
we can detect that correctly. In the reverse direction (i.e. changing
`TextField` to `CharField` and adding `unique_together`) the operations'
order is correct, `AlterField` and `AlterUniqueTogether`.
--
Ticket URL: <https://code.djangoproject.com/ticket/31186#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.86d91214f2ec7421a2b605adbdccd8d9%40djangoproject.com.
