#32503: AlterField migration to TextField with default fails on MySQL 8.0.13+
-------------------------------+------------------------------------
Reporter: Matt Westcott | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 3.0
Severity: Normal | Resolution:
Keywords: mysql default | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by Matt Westcott):
For anyone following along, I worked around this by splitting the
AlterField operation into two steps - first setting the field as non-
nullable, and then changing it to a TextField:
https://github.com/wagtail/wagtail/pull/6999/files
The breakage here still seems quite concerning though - given the
`preserve_default=False`, wouldn't we expect that the default value never
actually hits the database schema?
--
Ticket URL: <https://code.djangoproject.com/ticket/32503#comment:3>
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/064.c4c8e33e21c1778039d0600969163f5a%40djangoproject.com.
