Opened 6 years ago
Last modified 6 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 |
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()).
Attachments (1)
Change History (3)
by , 6 years ago
comment:1 by , 6 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 6 years ago
| Cc: | added |
|---|
Note:
See TracTickets
for help on using tickets.