#24595: alter field type on MySQL "forgets" nullability (and more) -------------------------------------+------------------------------------- Reporter: simonpercivall | Owner: Claude | Paroz <claude@…> Type: Bug | Status: closed Component: Migrations | Version: 1.7 Severity: Release blocker | Resolution: fixed Keywords: | 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 Claude Paroz <claude@…>): In [changeset:"ada0845ddaefb4437e1d49aa781fd87ed9628e8f" ada0845d]: {{{ #!CommitTicketReference repository="" revision="ada0845ddaefb4437e1d49aa781fd87ed9628e8f" [1.7.x] Fixed #24595 -- Prevented loss of null info in MySQL field alteration Thanks Simon Percivall for the report, and Simon Charette and Tim Graham for the reviews. Backport of 02260ea3f61b from master. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/24595#comment:10> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/072.a943865439e61ed015d967a9aada330f%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.