#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 Shai Berger <shai@…>):
In [changeset:"8363f217f2d60e73682e791f60b7f3c07a651316" 8363f217]:
{{{
#!CommitTicketReference repository=""
revision="8363f217f2d60e73682e791f60b7f3c07a651316"
[1.8.x] Fixed #24595 Oracle test failure
The only problem for Oracle was the test, which tested nullity on
text/char fields -- but Oracle interprets_empty_strings_as_null.
Backport of d5a0acc from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24595#comment:16>
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.029c41c2dc1483785e3d37f8e6543da4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
