#31492: Changing field type can cause unrelated nullability change in field on
Oracle.
-------------------------------------+-------------------------------------
Reporter: felixxm | Owner: nobody
Type: Bug | Status: new
Component: Database | Version: 3.0
layer (models, ORM) |
Severity: Normal | Keywords: oracle null
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changing a field type with implicit check constraint (e.g.
`PositiveIntegerField`) to a field without it (e.g. `CharField`) causes
nullability change because Django drops all check constraints in such
case, i.e. `NOT NULL` and `"COLUMN" >= 0` constraints (see
[https://github.com/django/django/blob/505fec6badba0622bbf97bb659188c3d62a9bc58/django/db/backends/base/schema.py#L645-L650
_alter_field()]).
--
Ticket URL: <https://code.djangoproject.com/ticket/31492>
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/050.011b1236d71f557dcc95a88022b95ce5%40djangoproject.com.
