#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
-------------------------------------+-------------------------------------
Changes (by Shai Berger <shai@…>):
* status: new => closed
* owner: => Shai Berger <shai@…>
* resolution: => fixed
Comment:
In [changeset:"773ec512b1872d4090b2ff8a759a85cc0f505bb9" 773ec512]:
{{{
#!CommitTicketReference repository=""
revision="773ec512b1872d4090b2ff8a759a85cc0f505bb9"
[1.7.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: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 [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.e1143d74462f7290900aa4e7df65665d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
