#32832: Adding nullable TextField/JSONField with default fails on MySQL 8.0.13+.
-------------------------------------+-------------------------------------
Reporter: Omkar Deshpande | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Migrations | Version: 3.2
Severity: Release blocker | Resolution: fixed
Keywords: django, mysql, | Triage Stage: Accepted
textfield, JsonField |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"fa0433d05f213afe4c67055006320f7aba4c8108" fa0433d0]:
{{{
#!CommitTicketReference repository=""
revision="fa0433d05f213afe4c67055006320f7aba4c8108"
Fixed #32832 -- Fixed adding BLOB/TEXT nullable field with default on
MySQL 8.0.13+.
Regression in d4ac23bee1c84d8e4610350202ac068fc90f38c0.
Thanks Omkar Deshpande for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32832#comment:6>
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/067.bfdb7ff349cfaf9a593b4805f643d880%40djangoproject.com.