#24846: MySQL Migration SchemaEditor default code is ignorant of other blob/text
data types
----------------------------+------------------------------
Reporter: adamchainz | Owner: adamchainz
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Keywords: mysql migrations
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------
#22424 added a default check for TextField and BinaryField, but it only
checks for the `longtext` and `longblob` data types which Django uses for
Text and Binary fields.
Some projects may be using custom field classes whose db_type is
`tinytext`, `mediumblob`, etc. which are also subject to the same no-
default rule, so the SchemaEditor should be made aware of that, otherwise
migrations may break.
--
Ticket URL: <https://code.djangoproject.com/ticket/24846>
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/053.29398005563ee2d72bf7b0d8830f8c00%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
