#33080: Changing nullability for fields which allow empty string should not
change
nullability on Oracle.
-------------------------------------+-------------------------------------
Reporter: Matt Hoskins | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: oracle null | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"338fc0e7f10f7ca781b059f2ff46e1a1a85c91f8" 338fc0e7]:
{{{
#!CommitTicketReference repository=""
revision="338fc0e7f10f7ca781b059f2ff46e1a1a85c91f8"
Fixed #33080 -- Preserved nullability of textual fields on Oracle.
Thanks Matt Hoskins for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33080#comment:2>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.09ac78beafe594f29b2663aa68c07b02%40djangoproject.com.
