Opened 5 years ago
Last modified 5 years ago
#31492 new Bug
Changing field type can cause unrelated nullability change in field on Oracle.
Description ¶
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 _alter_field()).
According to the ticket's flags, the next step(s) to move this issue forward are:
- To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR]
.
Change History (3)
by , 5 years ago
comment:1 by , 5 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 5 years ago
Cc: | added |
---|
Note:
See TracTickets
for help on using tickets.