#24817: Renaming a model field that has null=False makes it nullable in MySQL -------------------------------------+------------------------------------- Reporter: murfi | Owner: coldmind Type: Bug | Status: closed Component: Migrations | Version: 1.8 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 Tim Graham <timograham@…>): In [changeset:"927d90ee1ee4aa630a5a879b5fd75aa03a3341f7" 927d90ee]: {{{ #!CommitTicketReference repository="" revision="927d90ee1ee4aa630a5a879b5fd75aa03a3341f7" [1.7.x] Fixed #24817 -- Prevented loss of null info in MySQL field renaming. Backport of 80ad5472ce4b6ba6e94227422d0727371e97cdf0 from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/24817#comment:15> 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/063.51b4d288a0e506ebbfb6caaf79b47c92%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.