#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
-------------------------------------+-------------------------------------
Changes (by Claude Paroz <claude@…>):
* owner: => Claude Paroz <claude@…>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"02260ea3f61b2fe0a0178528526101ff578c7400" 02260ea]:
{{{
#!CommitTicketReference repository=""
revision="02260ea3f61b2fe0a0178528526101ff578c7400"
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.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24595#comment:8>
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.c5a9acc2ad936e4cca86f8980d45632b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
