#32503: AlterField migration to TextField with default fails on MySQL 8.0.13+
-------------------------------------+-------------------------------------
     Reporter:  Matt Westcott        |                    Owner:  Yuekui
         Type:  Bug                  |                   Status:  closed
    Component:  Migrations           |                  Version:  3.0
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  mysql default        |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"57146ba388b81aa9f7f47ad1dbca060871c9ca62" 57146ba]:
 {{{
 #!CommitTicketReference repository=""
 revision="57146ba388b81aa9f7f47ad1dbca060871c9ca62"
 [3.2.x] Fixed #32503 -- Fixed altering BLOB/TEXT field to non-nullable
 with default on MySQL 8.0.13+.

 MySQL 8.0.13+ supports defaults for BLOB/TEXT but not in the
 ALTER COLUMN statement.

 Regression in 6b16c91157512587017e9178d066ed1a683e7795.

 Thanks Matt Westcott for the report.

 Backport of 5e04e84d67da8163f365e9f5fcd169e2630e2873 from main
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32503#comment:9>
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.2baedf4efe6d9082b2e9e5600a78fbdc%40djangoproject.com.

Reply via email to