#24595: alter field type on MySQL "forgets" nullability (and more)
-------------------------------------+-------------------------------------
Reporter: simonpercivall | Owner: Shai
| Berger <shai@…>
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by shaib):
Well, for some reason the commit hook missed it on master, but just to
clarify,
[changeset:"d5a0accaa090e4e65486930dbddaae5ad72aca3d" d5a0acc] fixed the
problem there.
--
Ticket URL: <https://code.djangoproject.com/ticket/24595#comment:17>
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/072.87f64ecd4a977ef14696237acac66df0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
