Opened 5 years ago

Last modified 5 years ago

#31492 new Bug

Changing field type can cause unrelated nullability change in field on Oracle.

Reported by: Mariusz Felisiak Owned by: nobody
Component: Database layer (models, ORM) Version: 3.0
Severity: Normal Keywords: oracle null
Cc: Ian Bottomley Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no
Pull Requests:How to create a pull request

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 Mariusz Felisiak, 5 years ago

Attachment: test.py added

comment:1 by Carlton Gibson, 5 years ago

Triage Stage: UnreviewedAccepted

comment:2 by Ian Bottomley, 5 years ago

Cc: Ian Bottomley added
Note: See TracTickets for help on using tickets.
Back to Top